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

Semi-sync slave plugin assumes only one master

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Duplicate
    • 10.0.4
    • None
    • None
    • None

    Description

      Current semi-sync slave plugin implementation assumes that MariaDB has only one master and only one slave IO thread. As an example it has global variables semi_sync_need_reply and rpl_semi_sync_slave_status which should be per-master. Also I'd think object repl_semisync_slave should be per-master too.
      As general MariaDB design is done for multi-master replication, semi-sync slave plugin should be adjusted for that too.

      Attachments

        Issue Links

          Activity

            This shortcoming is documented here https://kb.askmonty.org/en/multi-source-replication/#todo as a limitation of the current implementation, and is waiting to be fixed as MDEV-3793 .

            elenst Elena Stepanova added a comment - This shortcoming is documented here https://kb.askmonty.org/en/multi-source-replication/#todo as a limitation of the current implementation, and is waiting to be fixed as MDEV-3793 .

            Closing as a duplicate of MDEV-3793.
            If you think it's not quite a duplicate and should be considered separately, please feel free to comment/re-open it.

            elenst Elena Stepanova added a comment - Closing as a duplicate of MDEV-3793 . If you think it's not quite a duplicate and should be considered separately, please feel free to comment/re-open it.

            People

              Unassigned Unassigned
              pivanof Pavel Ivanov
              Votes:
              0 Vote for this issue
              Watchers:
              3 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.