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

Allow SELECT to succeed even when node is not ready

Details

    Description

      Originally logged here : https://github.com/codership/mysql-wsrep/issues/36

      The idea is to introduce a new session variable "wsrep_dirty_reads" to enable SELECT to succeed even when the node is not ready and rejecting commands with ER_UNKNOWN_COMMAND.

      Attachments

        Issue Links

          Activity

            nirbhay_c Nirbhay Choubey (Inactive) created issue -
            nirbhay_c Nirbhay Choubey (Inactive) made changes -
            Field Original Value New Value
            Status Open [ 1 ] In Progress [ 3 ]
            nirbhay_c Nirbhay Choubey (Inactive) added a comment - http://lists.askmonty.org/pipermail/commits/2015-January/007299.html
            nirbhay_c Nirbhay Choubey (Inactive) made changes -
            Assignee Nirbhay Choubey [ nirbhay_c ] Jan Lindström [ jplindst ]
            Status In Progress [ 3 ] In Review [ 10002 ]

            Is this your solution for "not ready" failures in mysql-test?

            serg Sergei Golubchik added a comment - Is this your solution for "not ready" failures in mysql-test?

            No, its a separate feature.

            nirbhay_c Nirbhay Choubey (Inactive) added a comment - No, its a separate feature.

            Ok to push.

            jplindst Jan Lindström (Inactive) added a comment - Ok to push.
            jplindst Jan Lindström (Inactive) made changes -
            Assignee Jan Lindström [ jplindst ] Nirbhay Choubey [ nirbhay_c ]
            Status In Review [ 10002 ] Stalled [ 10000 ]
            nirbhay_c Nirbhay Choubey (Inactive) added a comment - Patch: https://github.com/MariaDB/server/commit/0105bf349a44f33fff3410af1db31d4c6116f14a KB entry: https://mariadb.com/kb/en/mariadb/documentation/managing-mariadb/replication/galera/galera-cluster-system-variables/#wsrep_dirty_reads
            nirbhay_c Nirbhay Choubey (Inactive) made changes -
            Fix Version/s 10.1.3 [ 18000 ]
            Fix Version/s 10.1 [ 16100 ]
            Resolution Fixed [ 1 ]
            Status Stalled [ 10000 ] Closed [ 6 ]
            nirbhay_c Nirbhay Choubey (Inactive) made changes -
            Fix Version/s 5.5.42-galera [ 18100 ]
            Fix Version/s 10.0.16-galera [ 18101 ]
            nirbhay_c Nirbhay Choubey (Inactive) added a comment - http://bazaar.launchpad.net/~maria-captains/maria/maria-5.5-galera/revision/3559 http://bazaar.launchpad.net/~maria-captains/maria/maria-10.0-galera/revision/3921
            nirbhay_c Nirbhay Choubey (Inactive) made changes -
            Component/s wsrep [ 11500 ]
            Component/s Galera [ 10124 ]
            ratzpo Rasmus Johansson (Inactive) made changes -
            Workflow MariaDB v2 [ 59240 ] MariaDB v3 [ 64844 ]
            erichowey Eric Howey made changes -
            erichowey Eric Howey made changes -
            erichowey Eric Howey made changes -
            erichowey Eric Howey made changes -
            Comment [ I would like to request that wsrep_dirty_reads be elevated to a *global* variable. A lot of people have complex application configurations that would make appending this before each query a difficult task. MySQL has made this variable a global one as of 5.6.26-25.12. I think it would be a good idea for MariaDB to do it as well. https://www.percona.com/doc/percona-xtradb-cluster/5.6/wsrep-system-index.html#wsrep_dirty_reads ]
            serg Sergei Golubchik made changes -
            Workflow MariaDB v3 [ 64844 ] MariaDB v4 [ 132508 ]

            People

              nirbhay_c Nirbhay Choubey (Inactive)
              nirbhay_c Nirbhay Choubey (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 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.