Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 10.4(EOL)
    • 10.4.19, 10.5.10
    • Galera
    • None

    Description

      • Disallow setting wsrep_on = 1 if wsrep_provider is unset. Also, move
        wsrep_on_basic from sys_vars to wsrep suite: this test now requires
        to run with wsrep_provider set
      • Disallow setting @@session.wsrep_on = 1 when @@global.wsrep_on = 0
      • Handle the case where a new connection turns @@global.wsrep_on from
        off to on. In this case we would miss a call to wsrep_open, causing
        unexpected states in wsrep::client_state (causing assertions).
      • Disable wsrep.MDEV-22443 because it is no longer possible to enable
        wsrep_on, if server is started with wsrep_provider='none'

      Attachments

        People

          jplindst Jan Lindström (Inactive)
          jplindst Jan Lindström (Inactive)
          Votes:
          0 Vote for this issue
          Watchers:
          1 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.