Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-36170

Deprecate the option --master-retry-count in favor of CHANGE MASTER TO Master_Retry_Count

Details

    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

          New Feature - A new feature of the product, which has yet to be developed. MDEV-25674 No SQL variable for master_retry_count setting

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          Activity

            Ascending order - Click to sort in descending order
            ParadoxV5 Jimmy Hú created issue -
            ParadoxV5 Jimmy Hú made changes -
            Field Original Value New Value
            ParadoxV5 Jimmy Hú added a comment -

            P.S. Our MTR tests would have to migrate too.

            ParadoxV5 Jimmy Hú added a comment - P.S. Our MTR tests would have to migrate too.
            knielsen Kristian Nielsen added a comment -

            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.

            knielsen Kristian Nielsen added a comment - 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.
            knielsen Kristian Nielsen made changes -
            Fix Version/s N/A [ 14700 ]
            Resolution Won't Fix [ 2 ]
            Status Open [ 1 ] Closed [ 6 ]

            People

              Unassigned Unassigned
              ParadoxV5 Jimmy Hú
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.