Uploaded image for project: 'MariaDB MaxScale'
  1. MariaDB MaxScale
  2. MXS-7561

Readwritesplit synchronizes transactions while the primary is throttled

    XMLWordPrintable

Details

    • New Feature
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • None
    • 26.10.0
    • readwritesplit
    • None
    • MXS-SPRINT-280
    • Hide
      Readwritesplit automatically enables `sync_transaction` if the current primary
      server is being throttled. Once throttling stops, `sync_transaction` is
      disabled. See
      [sync_transaction_throttle_rate]({maxscale}/reference/maxscale-routers/maxscale-readwritesplit#sync_transaction_throttle_rate)
      for more information.
      Show
      Readwritesplit automatically enables `sync_transaction` if the current primary server is being throttled. Once throttling stops, `sync_transaction` is disabled. See [sync_transaction_throttle_rate]({maxscale}/reference/maxscale-routers/maxscale-readwritesplit#sync_transaction_throttle_rate) for more information.

    Description

      MXS-6572 adds the foundation for transaction throttling by adding a server status bit that when detected by readwritesplit will cause it to throttle the transactions if it's configured in the appropriate configuration.

      The only problem is that the configuration is not the default configuration and it would be beneficial for the throttling to be possible even without manually enabled transaction synchronization.

      The goal of this task is to make it so that in the default readwritesplit configuration, which has sync_transaction=none, the throttling will start with a pre-defined configuration if it's not yet enabled.

      Attachments

        Issue Links

          Activity

            People

              markus makela markus makela
              markus makela markus makela
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - 1h Original Estimate - 1h
                  1h
                  Remaining:
                  Remaining Estimate - 0d
                  0d
                  Logged:
                  Time Spent - 0.75d
                  0.75d

                  Git Integration

                    Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.