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

parallel slave may not ignore ER_CONNECTION_KILLED error

    XMLWordPrintable

Details

    • Can result in hang or crash
    • Hide
      Fixed an issue where a parallel replica configured to skip ER_CONNECTION_KILLED (i.e. --slave-skip-errors=1927) can hang or crash because it honored this configuration, but should not (this error code is internally repurposed for replication worker threads and cannot be ignored).
      Show
      Fixed an issue where a parallel replica configured to skip ER_CONNECTION_KILLED (i.e. --slave-skip-errors=1927) can hang or crash because it honored this configuration, but should not (this error code is internally repurposed for replication worker threads and cannot be ignored).

    Description

      As pointed by Kristian neither replication tests nor production slave server configuration should not instruct the server to ignore --slave_skip_errors=1927 ER_CONNECTION_KILLED error on the parallel slave.

      This ticket is to make sure the slave service to examine any skipped errors on this matter
      and don't if the error is in the skip-list.

      Attachments

        Issue Links

          Activity

            People

              Elkin Andrei Elkin
              Elkin Andrei Elkin
              Andrei Elkin Andrei Elkin
              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.