Uploaded image for project: 'MariaDB Connector/C++'
  1. MariaDB Connector/C++
  2. CONCPP-4

Failover capabilities for Connector/C++

Details

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

    Description

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

      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.

      UPDATE: This task would cover the failover, CONCPP-73 the loadbalancing

      Attachments

        Issue Links

          is blocked by

          New Feature - A new feature of the product, which has yet to be developed. CONC-365 Failover capabilities

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed
          relates to

          New Feature - A new feature of the product, which has yet to be developed. CONCPP-73 Loadbalancing for Connector/C++

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          New Feature - A new feature of the product, which has yet to be developed. CONJS-169 Support failover and/or high-availability/load-balancing from Node.JS connector

          • Major - Major loss of function.
          • Closed

          New Feature - A new feature of the product, which has yet to be developed. CONPY-44 Failover capabilities for Connector/Python

          • Major - Major loss of function.
          • Closed

          New Feature - A new feature of the product, which has yet to be developed. ODBC-116 Failover capabilities for Connector/ODBC

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Task - A task that needs to be done. R2DBC-21 Failover capabilities for Connector/R2DBC

          • Major - Major loss of function.
          • Closed

          Activity

            Ascending order - Click to sort in descending order
            Lawrin Lawrin Novitsky added a comment - - edited

            It will actually derive those capabilities from C/J. They won't be in first version, though. But lot's of code is already there. It's just would be too much for first version.

            Lawrin Lawrin Novitsky added a comment - - edited It will actually derive those capabilities from C/J. They won't be in first version, though. But lot's of code is already there. It's just would be too much for first version.
            Lawrin Lawrin Novitsky added a comment -

            Based on Connector/C v3.3 feature. Syntax for hosts definition is the same, as in the C/J
            jdbc:mariadb:sequential://host1,host2,host3/testdb
            Single host: <host>[:port]. IPv6 address should be enclosed in square
            brackets like [::1].
            C/C submodule has been moved to use 3.3 branch by the commit.

            Lawrin Lawrin Novitsky added a comment - Based on Connector/C v3.3 feature. Syntax for hosts definition is the same, as in the C/J jdbc:mariadb:sequential://host1,host2,host3/testdb Single host: <host> [:port] . IPv6 address should be enclosed in square brackets like [::1] . C/C submodule has been moved to use 3.3 branch by the commit.

            People

              Lawrin Lawrin Novitsky
              GeoffMontee Geoff Montee (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              5 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.