Details
-
Type:
Task
-
Status: Open
-
Priority:
Minor
-
Resolution: Unresolved
-
Fix Version/s: 10.2
-
Component/s: None
-
Labels:None
Description
Parallel Replication in MariaDB would benefit from some improvements to behavior, usability, and diagnostics.
It may be better to set this up as some sort of "thread pool” with a maximum number of worker threads and have the default set to say 10. If nothing happens concurrently then no more threads are used; if it does they are up to the configured number. That’s easier for a DBA to manage rather than guessing as now an arbitrary number.
Also of interest would be some way to measure the actual concurrency. It may fluctuate quite a lot but having some way to see the maximum and “average”
number of active SQL threads would make it clear (perhaps) if the configured number is too low or too high. Right now it’s not clear to me how to monitor this and therefore how to know the setting is good. With many replication chains to monitor hand-tweaking on each one is a nuisance so a more flexible solution would certainly be useful if that’s possible.
Gliffy Diagrams
Attachments
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions