Details
-
Task
-
Status: Closed (View Workflow)
-
Trivial
-
Resolution: Won't Fix
-
None
Description
Once MDEV-25674 adds CHANGE MASTER [optional multi-source name] TO Master_Retry_Count=..., the pan-connection option --master-retry-count will have little-to-no value.
It could therefore be deprecated or at least discouraged, as in MySQL.
Attachments
Issue Links
- split from
-
MDEV-25674 No SQL variable for master_retry_count setting
-
- Closed
-
We do not deprecate things that will break backwards compatibility unless there is a very good technical need/reason to do so.
The --master-retry-count works fine as a default for the value, and will continue to do so for any existing system setup that is already using it. There is no need to discourage its use either.
It is very important that the millions of existing systems up there can be upgraded without being disturbed by unnecessary changes that are not backwards compatible.