[MXS-2456] Add cap for number of attempts to replay a transaction. Created: 2019-04-26 Updated: 2019-05-02 Resolved: 2019-05-02 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | readwritesplit |
| Affects Version/s: | None |
| Fix Version/s: | 2.4.0 |
| Type: | Task | Priority: | Major |
| Reporter: | Johan Wikman | Assignee: | markus makela |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Sprint: | MXS-SPRINT-81 |
| Description |
|
With Clustrix, a transaction can be replayed not only because of a connection breakage but also because of errors returned by Clustrix. So as not to end up in an endless replay loop in case a replayed transaction - for whatever reason - ends up with a retriable error, some form of cap should be introduced. |
| Comments |
| Comment by markus makela [ 2019-04-26 ] |
|
A timeout might be an interesting alternative. |
| Comment by markus makela [ 2019-05-02 ] |
|
Added transaction_replay_attempts that limits the number of replay attempts. The default value is 5 attempts. |