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

Start and stop replication to Exasol at runtime

    XMLWordPrintable

Details

    • New Feature
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 25.10.3
    • 26.10.0
    • exasol-cdc
    • None
    • MXS-SPRINT-276, MXS-SPRINT-277
    • Hide
      Exasol CDC is now started and stopped with the binlogrouter module commands
      `cdc-start` and `cdc-stop`, without restarting MaxScale. Stopping it does not
      affect the replication of the binlogrouter itself, and whether it is running
      is remembered over restarts. A new Exasol CDC is stopped until `cdc-start` is
      run. See
      [Starting and Stopping]({maxscale}/reference/maxscale-routers/maxscale-exasol-cdc#starting-and-stopping)
      for more information.
      Show
      Exasol CDC is now started and stopped with the binlogrouter module commands `cdc-start` and `cdc-stop`, without restarting MaxScale. Stopping it does not affect the replication of the binlogrouter itself, and whether it is running is remembered over restarts. A new Exasol CDC is stopped until `cdc-start` is run. See [Starting and Stopping]({maxscale}/reference/maxscale-routers/maxscale-exasol-cdc#starting-and-stopping) for more information.

    Description

      Currently, stopping or starting CDC replay requires commenting out the config section and restarting MaxScale. This is disruptive and manual.

      Ask: Add a maxctrl command (and corresponding REST API endpoint) to start/stop CDC replay without editing config or restarting MaxScale.

      Acceptance Criteria:

      • maxctrl supports a command to stop CDC replay on a running MaxScale instance without a restart.
      • maxctrl supports a command to start CDC replay on a running instance without a restart.
      • Equivalent REST API endpoints exist for start/stop, usable by external tooling/scripts.
      • Stopping CDC does not stop the binlogrouter or affect binlog replication.
      • Current CDC state (running/stopped) is queryable via maxctrl/API.

      Attachments

        Activity

          People

            nantti Niclas Antti
            allen.herrera Allen Herrera
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Time Tracking

                Estimated:
                Original Estimate - 2d
                2d
                Remaining:
                Remaining Estimate - 0d
                0d
                Logged:
                Time Spent - 7h Time Not Required
                7h

                Git Integration

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