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

More control over primary node for columnstore 5.x

    XMLWordPrintable

Details

    • New Feature
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Won't Do
    • None
    • N/A
    • N/A
    • None

    Description

      with mcsadmin the primary can be chossed with

      Choose Primary

      This function is lost and no equivalent in cmapi/maxscale exists.

      In the maxscale module csmon is a function
      primary

      "The primary parameter controls which server is chosen as the master server. "

      csmon is deprecated and only for 1.2 and below.

      So we need a feature, where a user can define a primary
      and maxscale keep this primary as primary back after columnstore choosed a different node as primary after a failover from columnstore side.

      Attachments

        Issue Links

          Activity

            People

              Richard Richard Stracke
              Richard Richard Stracke
              Votes:
              0 Vote for this issue
              Watchers:
              2 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.