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

detailize the semisync replication magic number error

Details

    Description

      2023-10-02 12:31:43 1 [ERROR] Read semi-sync reply magic number error

      can be seen on the master side of a replication configuration which is not common though
      can appear as a result of not properly set proxy program in between of the master and a slave.
      An attempt to misuse the master side file descriptor could and should be addressed at least
      with printing down the hexdump of the magic number error's packet.

      Attachments

        Issue Links

          causes

          Bug - A problem which impairs or prevents the functions of the product. MDEV-32961 Semi-sync Primary Segfaults on Net Error

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

          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

          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
            Elkin Andrei Elkin added a comment - - edited

            monty, this ticket is of course not meant to be a solution. The idea is to capture the details of corrupted packet just to have
            more data to think where it comes from etc.
            It may be not from a proxy, and could be from a mariadb plugin or other "X".

            To remind you about audit plugin that was used to write into binlog file, and that was caught by reading into details of those messages.
            Having more to the magic error in the error log also a note level message with the hexdump can't hurt obviously either.

            I hope that clears your doubt.

            Elkin Andrei Elkin added a comment - - edited monty , this ticket is of course not meant to be a solution. The idea is to capture the details of corrupted packet just to have more data to think where it comes from etc. It may be not from a proxy, and could be from a mariadb plugin or other "X". To remind you about audit plugin that was used to write into binlog file, and that was caught by reading into details of those messages. Having more to the magic error in the error log also a note level message with the hexdump can't hurt obviously either. I hope that clears your doubt.
            Elkin Andrei Elkin added a comment -

            Howdy Brandon!

            Could you please check a simple few-liner.
            I am all ears for anything to improve!

            Andrei

            Elkin Andrei Elkin added a comment - Howdy Brandon! Could you please check a simple few-liner. I am all ears for anything to improve! Andrei
            bnestere Brandon Nesterenko added a comment -

            Left a comment for consideration, and rpl.rpl_semi_sync_shutdown_await_slaves needs a fix to ignore the new error; otherwise looks good!

            bnestere Brandon Nesterenko added a comment - Left a comment for consideration, and rpl.rpl_semi_sync_shutdown_await_slaves needs a fix to ignore the new error; otherwise looks good!

            People

              Elkin Andrei Elkin
              Elkin Andrei Elkin
              Votes:
              2 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.