Uploaded image for project: 'MariaDB Connector/J'
  1. MariaDB Connector/J
  2. CONJ-601

Best Practices for Aurora Cluster Reader Endpoint Failover

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: 2.2.3
    • Fix Version/s: None
    • Component/s: aurora, Failover, question
    • Labels:
      None
    • Environment:
      Aurora MySQL

      Description

      I'm trying to connect to Aurora with the MariaDB Connector and having a hard time figuring out how I should connect. I have two applications: one is read/write, and one is read-only. I'd like to setup failover properly for both applications. Based on what I can understand from documentation I've set up my URLs like this:

      For the read/write application, I have
      jdbc:mariadb:aurora://somecluster.cluster-lettersanddigits.us-east-1.rds.amazonaws.com:3306/db. Will this failover properly given a change in the master instance? Or do I have to specify additional parameters?

      For the read-only application I would like to connect to the cluster reader endpoint, for which I do not see documentation in the Connector. My URL looks like jdbc:mariadb://somecluster.cluster-ro-lettersanddigits.us-east-1.rds.amazonaws.com:3306/db. When I try to include aurora: in the reader endpoint URL, connection acquisition attempts hang indefinitely. My understanding is that as I have it, I will not see great failover properties from the read-only application. However AWS specifies that the cluster reader endpoint has certain failover properties itself, so I'm not sure how to leverage the Connector properly to get the best failover behavior.

      Is there documentation with respect to using the MariaDB Connector with Aurora cluster reader endpoints?

        Attachments

          Activity

            People

            Assignee:
            diego dupin Diego Dupin
            Reporter:
            andrewparmet Andrew Parmet
            Votes:
            2 Vote for this issue
            Watchers:
            6 Start watching this issue

              Dates

              Created:
              Updated:

                Git Integration