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

No warning , if set server_id on replica to the same server_id on the master

Details

    • Bug
    • Status: Closed (View Workflow)
    • Critical
    • Resolution: Not a Bug
    • None
    • N/A
    • Replication
    • None

    Description

      IF a replica was set the server_id on the same value as the master
      set global server_id = master_server_id;

      it have an immediate effect without warning during running replication.

      Only after a restart the well known message occured.

      [ERROR] Slave I/O: Fatal error: The slave I/O thread stops because master and slave have equal MariaDB server ids;

      An error should be thrown immediate. To Client and error log

      Attachments

        Activity

          Ascending order - Click to sort in descending order
          Richard Richard Stracke created issue -
          Richard Richard Stracke made changes -
          Field Original Value New Value
          Component/s Replication [ 10100 ]
          Description
          IF a replica was set the server_id on the same value as the master
          set global server_id = master_server_id;

          it have an immediate effect without warning during running replication.

          Only after a restart the well known message occured.



          {code:java}
          [ERROR] Slave I/O: Fatal error: The slave I/O thread stops because master and slave have equal MariaDB server ids;
          {code}


          An error should be thrown immediate. To Client and error log
          		IF a replica was set the server_id on the same value as the master
          set global server_id = master_server_id;

          it have an immediate effect without warning during running replication.

          Only after a restart the well known message occured.



          {code:java}
          [ERROR] Slave I/O: Fatal error: The slave I/O thread stops because master and slave have equal MariaDB server ids;
          {code}


          An error should be thrown immediate. To Client and error log
          JIraAutomate JiraAutomate made changes -
          Fix Version/s 10.5 [ 23123 ]
          Fix Version/s 10.6 [ 24028 ]
          julien.fritsch Julien Fritsch made changes -
          Assignee Brandon Nesterenko [ JIRAUSER48702 ]
          julien.fritsch Julien Fritsch made changes -
          Status Open [ 1 ] Confirmed [ 10101 ]
          julien.fritsch Julien Fritsch made changes -
          Priority Major [ 3 ] Critical [ 2 ]
          knielsen Kristian Nielsen added a comment -

          The current behavior matches all other settings that have both global and session values. Setting the global does not modify existing sessions (a running slave thread corresponds to a session here).

          If this was changed to work differently for server_id, it would be inconsistent.

          knielsen Kristian Nielsen added a comment - The current behavior matches all other settings that have both global and session values. Setting the global does not modify existing sessions (a running slave thread corresponds to a session here). If this was changed to work differently for server_id, it would be inconsistent.
          serg Sergei Golubchik made changes -
          Fix Version/s N/A [ 14700 ]
          Fix Version/s 10.5 [ 23123 ]
          Fix Version/s 10.6 [ 24028 ]
          Resolution Not a Bug [ 6 ]
          Status Confirmed [ 10101 ] Closed [ 6 ]

          People

            bnestere Brandon Nesterenko
            Richard Richard Stracke
            Votes:
            0 Vote for this issue
            Watchers:
            6 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.