Details

    • New Feature
    • Status: Closed (View Workflow)
    • Critical
    • Resolution: Fixed
    • None
    • 3.3.0
    • None
    • None

    Description

      Goal is to permit setting some failover capability on connector level.

      Configuration must permit setting multiple hosts/ports. Then, when trying to establish a connection, connector will trying to connect those hosts sequentially until success or throwing error if last host connection fails.

      This would permit failover on multiple maxscale instances, avoiding use additional tools that monitor maxscales state.

      "failover" in the scope of this task is trying hosts from the list of alternative hosts until connection succeeds. It should work on the first connect and on auto-reconnect. Nothing else is in the scope, no replaying of transactions, for example.

      Attachments

        Issue Links

          Activity

            ralf.gebhardt Ralf Gebhardt added a comment -

            Blocker added as Connector/C needs to provide the functionality, Connector/ODBC will only need to provide functionality in the connection string.

            ralf.gebhardt Ralf Gebhardt added a comment - Blocker added as Connector/C needs to provide the functionality, Connector/ODBC will only need to provide functionality in the connection string.

            People

              georg Georg Richter
              ralf.gebhardt Ralf Gebhardt
              Votes:
              2 Vote for this issue
              Watchers:
              9 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.