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

Master should also log server-id collisions

Details

    • Bug
    • Status: Confirmed (View Workflow)
    • Minor
    • Resolution: Unresolved
    • 10.2.7
    • 10.2(EOL)
    • Replication
    • None

    Description

      With MDEV-11177 fixed we are now getting duplicate slave id error log messages on the slave side. On the master side either nothing gets logged though, or with log-warnings=3 and a pair of slaves with duplicate IDs the master error log is flooded with messages of the form

      2017-08-04 9:42:07 140315054417664 [Note] Start binlog_dump to slave_server(12), pos(master.000001, 520)

      several times per second

      Attachments

        Issue Links

          Activity

            Worse even, Start binlog_dump to slave_server... is logged on level 2, which is default in 10.2.

            I'm not sure how valuable it is to have messages about duplicate slave IDs on master, as it's the problem that needs to be solved on the slave side, master can't do much about it. But if there is a demand for it, and as long as it doesn't flood the log, then of course why not.

            elenst Elena Stepanova added a comment - Worse even, Start binlog_dump to slave_server ... is logged on level 2, which is default in 10.2. I'm not sure how valuable it is to have messages about duplicate slave IDs on master, as it's the problem that needs to be solved on the slave side, master can't do much about it. But if there is a demand for it, and as long as it doesn't flood the log, then of course why not.

            People

              Elkin Andrei Elkin
              hholzgra Hartmut Holzgraefe
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:

                Git Integration

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