Details
-
New Feature
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
None
-
None
-
MXS-SPRINT-280
-
Description
MXS-6572 adds the foundation for transaction throttling by adding a server status bit that when detected by readwritesplit will cause it to throttle the transactions if it's configured in the appropriate configuration.
The only problem is that the configuration is not the default configuration and it would be beneficial for the throttling to be possible even without manually enabled transaction synchronization.
The goal of this task is to make it so that in the default readwritesplit configuration, which has sync_transaction=none, the throttling will start with a pre-defined configuration if it's not yet enabled.
Attachments
Issue Links
- is blocked by
-
MXS-7589 sync_transaction_count is not limited to the number of configured backend servers
-
- Closed
-
-
MXS-7590 Failed transaction sync still updates GTID position
-
- Closed
-
-
MXS-7592 Interrupted lag probe is counted as a successful one
-
- Closed
-
-
MXS-7593 sync_transaction_timeout is not always respected
-
- Closed
-
-
MXS-7594 sync_transaction does not retry an interrupted sync
-
- Closed
-
-
MXS-7596 sync_transaction accepts stale sync message as a fresh one
-
- Closed
-
-
MXS-7601 Stale connection with pending sync should be ignored
-
- Closed
-
-
MXS-7602 Sync_transaction timers are too coarse
-
- Closed
-
-
MXS-7604 Very large duration values cause signed integer overflow
-
- Closed
-
-
MXS-7607 sync_transaction sends redundant syncs to multi-statement queries
-
- Closed
-
-
MXS-7610 Signed overflow in duration calculation of sync_transaction
-
- Closed
-
- is part of
-
MXS-6235 prepare for switchover by throttling writes - keep replication lag low
-
- Open
-