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

slave_compressed_protocol doesn't work properly with semi-sync replication

Details

    Description

      slave_compressed_protocol doesn't work properly with semi-sync replication. When it is enabled, It leads to intermittent SBM (Slave Behind Master) spikes and sometime gives below error. 

      2021-01-29 15:34:40 11 [ERROR] Read semi-sync reply magic number error
      		 
      2021-01-29 15:34:50 9 [Warning] Timeout waiting for reply of binlog (file: master-bin.000001, pos: 479), semi-sync up to file master-bin.000001, position 329.
      		 
      2021-01-29 15:34:50 9 [Note] Semi-sync replication switched OFF.

      Looks like this is upstream bug. https://bugs.mysql.com/bug.php?id=86230
      "The receiver thread for semisynchronous replication was not able to receive acknowledgements from slaves that used compression of the master/slave protocol (slave_compressed_protocol = ON) "

      Attachments

        Issue Links

          causes

          Bug - A problem which impairs or prevents the functions of the product. MDEV-32655 rpl_semi_sync_slave_compressed_protocol.test assert_only_after is wrong

          • Major - Major loss of function.
          • Closed
          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-32551 "Read semi-sync reply magic number error" warnings on master

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Activity

            Ascending order - Click to sort in descending order
            sujatha.sivakumar Sujatha Sivakumar (Inactive) added a comment -

            Hello Andrei,

            Can you please review the fix for MDEV-24773

            Patch: https://github.com/MariaDB/server/commit/4f9c5a8cf545133c3d29c0de3f7e2e57564607f2

            BuildBot Test: http://buildbot.askmonty.org/buildbot/grid?category=main&branch=bb-10.3-sujatha

            Thank you

            sujatha.sivakumar Sujatha Sivakumar (Inactive) added a comment - Hello Andrei, Can you please review the fix for MDEV-24773 Patch: https://github.com/MariaDB/server/commit/4f9c5a8cf545133c3d29c0de3f7e2e57564607f2 BuildBot Test: http://buildbot.askmonty.org/buildbot/grid?category=main&branch=bb-10.3-sujatha Thank you
            Elkin Andrei Elkin added a comment -

            The patch looks good to appove. Please find one note of a general character on github. Thank you for creative efforts and, naturally, to Venkat !

            Elkin Andrei Elkin added a comment - The patch looks good to appove. Please find one note of a general character on github. Thank you for creative efforts and, naturally, to Venkat !
            sujatha.sivakumar Sujatha Sivakumar (Inactive) added a comment -

            Fixed is implemented in 10.3.29.

            Patch was cherry-picked to higher versions and tested on buildbot.
            No merge conflicts were observed.

            10.4 patch: https://github.com/MariaDB/server/commit/a2ba707c3feb4870ca7760abaef8dc3389f8da26
            10.5 patch: https://github.com/MariaDB/server/commit/f19408e8519071e9410124f8ec4e5b7733d334e3

            sujatha.sivakumar Sujatha Sivakumar (Inactive) added a comment - Fixed is implemented in 10.3.29. Patch was cherry-picked to higher versions and tested on buildbot. No merge conflicts were observed. 10.4 patch: https://github.com/MariaDB/server/commit/a2ba707c3feb4870ca7760abaef8dc3389f8da26 10.5 patch: https://github.com/MariaDB/server/commit/f19408e8519071e9410124f8ec4e5b7733d334e3

            People

              sujatha.sivakumar Sujatha Sivakumar (Inactive)
              niljoshi Nilnandan Joshi
              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.