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

Consistency compromized after a CREATE TABLE command failed

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Duplicate
    • Affects Version/s: 5.5.37-galera
    • Fix Version/s: 5.5.43-galera, 10.0.17-galera
    • Component/s: wsrep
    • Environment:
      CentOS 6.5 x86_64
      Galera Cluster installed from MariaDB repository
      3 node with HAProxy to balance read (3 nodes) and write (1 node)

      Description

      2 of 3 nodes close server due to consistency compromized, after a CREATE TABLE command failed.
      The sql comand was:
      CREATE TABLE tab_test_tmp LIKE tab_test
      It failed because the table tab_test didn't exist.
      I attached the detailed log of a failed node.
      My question is: why this failed sql command has been "replicatated" to other cluster node, if the command failed?

      I can't reproduce the error because I don't have a testing cluster.

        Attachments

          Activity

            People

            Assignee:
            nirbhay_c Nirbhay Choubey (Inactive)
            Reporter:
            lgrio Lorenzo
            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.