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

Semi-Sync Replica can KILL a reässigned connection

    XMLWordPrintable

Details

    • Can result in unexpected behaviour

    Description

      When a semi-sync replica shuts down, it opens a second connection to KILL the original on the primary's side without verification.
      But the primary can have already KILLed its side of the connection due to this replica timing out (including due to misconfiguration) or as requested by a DBA.

      The self-KILL's error handling likely covers the consequence of KILLing an already-KILLed and now non-existent connection.
      But if the server also reässigns the replica's old CONNECTION_ID to someöne else, then this "graceful" self-KILL would unknowingly KILL that connection, nonëxistent or even reässigned connection.

      This problem would not occur if the replica also detected disconnection and force-stopped due to connection failure (after any @@master_retry_count).

      Attachments

        Issue Links

          Activity

            People

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

              Dates

                Created:
                Updated:

                Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - Not Specified
                  Not Specified
                  Logged:
                  Time Spent - 1h 50m
                  1h 50m

                  Git Integration

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