Details
-
New Feature
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
None
Description
It is currently very hard to diagnose slave lag problems. This ticket is to track work to extend the replica with various diagnostic capabilities to make it easier to track down performance issues.
One idea so far is to have dynamic profiling that only turns on when the slave starts lagging. For example, it could use the perf C API; or automatically capture thread stacks.
Estimations:
- 30 days for the design, dev and review
- 12 days for testing
- Total 42 mandays
Attachments
Issue Links
- includes
-
MDEV-21322 report slave progress to the master
-
- Stalled
-
- relates to
-
MDEV-7340 [PATCH] parallel replication status variables
-
- Open
-
-
MDEV-5296 No status information available for parallel replication
-
- Open
-
-
MDEV-41142 Deprecate rpl_semi_sync_master_trace_level/rpl_semi_sync_slave_trace_level
-
- Open
-