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

Server crashes in choose_best_splitting

Details

    • Bug
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • 10.11.2, 10.11.4
    • 10.11
    • Server
    • ProLiant DL360 Gen10, 48 cores, 128GB memory, Centos 8

    Description

      We have a primary with 2 replicas and have seen a crash where both replicas crash almost simultaneously at the same query. At other times during the day the same query has had no problems and unfortunately we have not managed to replicate this either.
      So far we have seen exactly the same behaviour only once more two weeks ago where a very similar query crashed both replication servers.
      In both cases there was a bulk import running on the primary server that got replicated to the crashing replicas, but on a different schema and table that is requested in the query.

      Attachments

        Issue Links

          Activity

            cbefin Christian Braeuner created issue -
            cbefin Christian Braeuner made changes -
            Field Original Value New Value
            Description We have a primary with 2 replicas and have seen a crashes in the last two weeks where both replicas crash almost simultaneously at the same query. At other times during the day the same query has had no problems and unfortunately we have not managed to replicate this either.
            So far we have seen exactly the same behaviour only once more two weeks ago where a very similar query crashed both servers.
            In both cases there was a bulk import running on the primary server that got replicated to the crashing replicas, but on a different schema and table that is requested in the query.
            We have a primary with 2 replicas and have seen a crash where both replicas crash almost simultaneously at the same query. At other times during the day the same query has had no problems and unfortunately we have not managed to replicate this either.
            So far we have seen exactly the same behaviour only once more two weeks ago where a very similar query crashed both replication servers.
            In both cases there was a bulk import running on the primary server that got replicated to the crashing replicas, but on a different schema and table that is requested in the query.
            alice Alice Sherepa made changes -
            alice Alice Sherepa made changes -
            cbefin Christian Braeuner made changes -
            Affects Version/s 10.11.2 [ 28523 ]
            cbefin Christian Braeuner made changes -
            Attachment 2023-08-03-mariaDB-logs.zip [ 71324 ]
            danblack Daniel Black made changes -
            danblack Daniel Black made changes -
            Assignee Sergei Petrunia [ psergey ]
            serg Sergei Golubchik made changes -
            Fix Version/s 10.11 [ 27614 ]
            alice Alice Sherepa made changes -
            alice Alice Sherepa made changes -
            cbefin Christian Braeuner made changes -
            Attachment 2023-11-08-mariaDB-logs.zip [ 72438 ]

            People

              psergei Sergei Petrunia
              cbefin Christian Braeuner
              Votes:
              2 Vote for this issue
              Watchers:
              7 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.