Details

    • New Feature
    • Status: Open (View Workflow)
    • Minor
    • Resolution: Unresolved
    • None
    • Galera
    • None

    Description

      A whiel ago, when one neede to execute DML changes (insert/update/delete) on a node without submitting them to the galera replication by setting sql_log_bon=off.

      while the fix is good, sometimes we can still have the need to modify datas in a single node of a cluster to avoid triggering massive SSTs and this is not doable anymore.

      can we introduce a session only dynamic variable that disable galera replication on commit :

      sqlprompt > set session wsrep_local_commit = yes;
      sqlprompt > bunch of DMLs
      sqlprompt > commit;
      sqlprompt > set session wsrep_local_commit = no;

      USE CASE :
      massive dataset (in the To range)
      one small table is messed up during an RSU delivery (a few 100s Mbs)

      triggering an SST i that case would be a waste of time and ressources while a simple set of DML instructions would solve the issue.

      Attachments

        Activity

          There are no comments yet on this issue.

          People

            Unassigned Unassigned
            SylvainArbaudie Sylvain ARBAUDIE
            Votes:
            1 Vote for this issue
            Watchers:
            1 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.