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

Implement rpl_semi_sync_source_wait_for_replica_count for semi-sync replication

Details

    • New Feature
    • Status: Closed (View Workflow)
    • Critical
    • Resolution: Duplicate
    • N/A
    • Replication
    • None

    Description

      MySQL 8.0 introduced this rather useful feature and it really should be implemented in MariaDB also. It controls how many replcas need to pick up a semi-sync replication event before the event is considered replicated on the primary.

      Attachments

        Issue Links

          duplicates

          Task - A task that needs to be done. MDEV-18983 Port rpl_semi_sync_master_wait_for_slave_count from MySQL

          • Major - Major loss of function.
          • Open

          Activity

            Descending order - Click to sort in ascending order
            ParadoxV5 Jimmy Hú added a comment -

            Both you and I should’ve searched for any existing issues with the older ‘slave’ terminology .

            ParadoxV5 Jimmy Hú added a comment - Both you and I should’ve searched for any existing issues with the older ‘slave’ terminology .
            ParadoxV5 Jimmy Hú added a comment -

            This is called rpl_semi_sync_master_wait_for_slave_count before MySQL’s version of MDEV-18777.
            It’d be rpl_semi_sync_primary_wait_for_replica_count in our ‘primary’ terminology.

            ParadoxV5 Jimmy Hú added a comment - This is called rpl_semi_sync_master_wait_for_slave_count before MySQL’s version of MDEV-18777 . It’d be rpl_semi_sync_primary_wait_for_replica_count in our ‘primary’ terminology.

            People

              Unassigned Unassigned
              karlsson Anders Karlsson
              Votes:
              0 Vote for this issue
              Watchers:
              4 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.