Uploaded image for project: 'MariaDB ColumnStore'
  1. MariaDB ColumnStore
  2. MCOL-3812

MariaDB asserts when connection closed

Details

    • Bug
    • Status: Closed (View Workflow)
    • Blocker
    • Resolution: Fixed
    • 1.5.3
    • 1.5.1
    • MDB Plugin
    • None
    • 2020-3, 2020-4, 2020-5, 2020-6, 2020-7

    Description

      When a connection is closed, ha_mcs_impl_close_connection() is executed. In previous versions it was optional to execute this:
      thd_set_ha_data(thd, hton, NULL);
      Since we believe in cleaning up our own stuff, we did this.

      In 10.5, this is no longer optional. Server asserts if we do this.

      Attachments

        Activity

          Ascending order - Click to sort in descending order
          David.Hall David Hall (Inactive) added a comment -

          QA: To test, you need a debug build to trigger the assert to signal. Just start up a debug version of columnstore 1.5, open a session, then close the session. mysqld would assert and crash. Patch should fix this.

          David.Hall David Hall (Inactive) added a comment - QA: To test, you need a debug build to trigger the assert to signal. Just start up a debug version of columnstore 1.5, open a session, then close the session. mysqld would assert and crash. Patch should fix this.
          dleeyh Daniel Lee (Inactive) added a comment -

          Build verified: 1.5.0-1 (Drone build #59)

          Verified on a debug build on Centos 7.

          dleeyh Daniel Lee (Inactive) added a comment - Build verified: 1.5.0-1 (Drone build #59) Verified on a debug build on Centos 7.

          People

            dleeyh Daniel Lee (Inactive)
            David.Hall David Hall (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 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.