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

Graceful shutdown of MaxScale when using more than one MaxScale instance

Details

    • New Feature
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Duplicate
    • None
    • N/A
    • failover
    • None

    Description

      The customer has to restart MaxScale in case of MaxScale upgrade or MaxScale maintenance (for example if MaxScale would start to take too many resources).

      The task is to implement a graceful shutdown of MaxScale without causing any notable interruptions to users that uses MaxScale to connect to MariaDB server.

      The logic would be as follows when requesting a graceful shutdown:

      • Move all connections to the other MaxScale
      • Shutdown MaxScale
      • One restart, move half of the connections from the other MaxScale to the current one.

      The customer can then repeat the above procedure with the other MaxScale if needed.

      Attachments

        Issue Links

          duplicates

          New Feature - A new feature of the product, which has yet to be developed. MXS-4153 Graceful Restart

          • Major - Major loss of function.
          • Open
          relates to

          Task - A task that needs to be done. MDEV-32053 New features requested by customer on 2023-08-28

          • Major - Major loss of function.
          • Open

          Activity

            monty Michael Widenius added a comment -

            Yes, MXS-4153 is the same thing, but this MXS is more explicit how it would work from the customers point of view.
            I suggest that someone takes that example from above and adds it to MXS-4153, after which one can declare this as a duplicate.
            Note that the resulting task MUST also be linked from https://jira.mariadb.org/browse/MDEV-32053 so that the customer can easily follow the progress of the task they think are important for them.

            monty Michael Widenius added a comment - Yes, MXS-4153 is the same thing, but this MXS is more explicit how it would work from the customers point of view. I suggest that someone takes that example from above and adds it to MXS-4153 , after which one can declare this as a duplicate. Note that the resulting task MUST also be linked from https://jira.mariadb.org/browse/MDEV-32053 so that the customer can easily follow the progress of the task they think are important for them.

            People

              JoeCotellese Joe Cotellese (Inactive)
              monty Michael Widenius
              Votes:
              2 Vote for this issue
              Watchers:
              6 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.