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

Clarify difference between ER_CONNECTION_KILLED (1927) and error 2013

    XMLWordPrintable

Details

    • Bug
    • Status: Confirmed (View Workflow)
    • Major
    • Resolution: Unresolved
    • 10.2, 10.3, 10.4, 10.5, 10.6, 10.7, 10.8
    • 10.4, 10.5, 10.6
    • None
    • None

    Description

      While writing MTR tests of procedure code, it's sometimes necessary to expect the current connection/thread to be killed.

      I've been using the following in my MTR .test files:

      --error ER_CONNECTION_KILLED
      call PROCEDURE_THAT_WILL_CAUSE_THIS_CONNECTION_TO_DIE();
      

      However, this occasionally results in tests failing

      mysqltest: At line X, PROCEDURE_THAT_WILL_CAUSE_THIS_CONNECTION_TO_DIE() failed with wrong errno 2013: 'Lost connection to MySQL server during query', instead of 1927...
      

      It would be useful to have clarity on when/why an MTR test can sometimes fail with error 2013 instead of error 1927/ER_CONNECTION_FAILED.

      • Is this a consequence of server- vs client-side timing of when the lost connection is detected?
      • Is there a way to ensure we consistently get only one result, and not the other?
      • If the variation is truly unavoidable, shouldn't all tests with --error ER_CONNECTION_KILLED also allow for --error 2013?

      Attachments

        Activity

          People

            Unassigned Unassigned
            dlenski Daniel Lenski
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:

              Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.