Details
-
Type:
Bug
-
Status: Open
-
Priority:
Minor
-
Resolution: Unresolved
-
Affects Version/s: 10.1.3
-
Fix Version/s: 10.1
-
Component/s: Replication
-
Labels:
Description
In optimistic parallel replication (MDEV-6676), we speculatively apply
transactions in parallel, even if they might conflict. If too many conflicts
happen, excessive retry might degrade performance.
The DBA needs some way to monitor for such problems. One good way would seem
to have an option to add to the slow query log any transactions that were
retried due to parallel replication conflicts. Possibly with extra information
such as duration of transaction and similar.
Gliffy Diagrams
Attachments
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions
I'm not sure that slow log is a good match for this kind of events