rpl_semi_sync_master_timeout Can it be changed to configurable
sona-yuan opened this issue · comments
What
Describe what this issue should address.
How
Describe how to address the issue.
Checklist
- Finish implementation of the issue
- Test all functions
- Have enough logs to trace activities
- Notify developers of necessary actions
No.
It's deliberately designed not to be configurable.
See docs/clustering.md for details.
However, if we consider RTO, some services that want higher continuity can accept sacrificing some data consistency. May I ask if we consider changing it to a configurable item in the future