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) added a comment - http://lists.askmonty.org/pipermail/commits/2015-January/007299.html

            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.
            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) 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

            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.