[MXS-2834] Transaction retrying on deadlock is not configurable Created: 2020-01-11 Updated: 2020-01-14 Resolved: 2020-01-14 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | readwritesplit |
| Affects Version/s: | 2.4.5 |
| Fix Version/s: | 2.4.6 |
| Type: | Bug | Priority: | Major |
| Reporter: | markus makela | Assignee: | markus makela |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Description |
|
The automatic retrying of transactions on deadlock is not always the desired behavior. If it is done in cases where deadlocks are acceptable, the resulting transaction checksum error is very misleading. By making this functionality configurable and disabling it by default, we allow applications that can handle deadlocks (e.g. sysbench) to perform normally. |
| Comments |
| Comment by markus makela [ 2020-01-11 ] |
|
Added a new parameter that controls whether the transactions are automatically replayed on deadlock: transaction_replay_retry_on_deadlock=[true|false] |