The Ultimate Guide to High Availability with MariaDB

MariaDB Connector/J 1.5.1 Release Notes

You are viewing an old version of this article. View the current version here.

The most recent Stable (GA) release of MariaDB Connector/J is:
MariaDB Connector/J 3.3.3

Download Release Notes Changelog Connector/J Overview

Release date: 16 Aug 2016

MariaDB Connector/J 1.5.1 is a Release candidate (RC) release.

For a description of MariaDB Connector/J see the About MariaDB Connector/J page

Notable Changes

Evolution

Aurora host auto-discovery

(CONJ-325)

Aurora now auto discover nodes from cluster endpoint.

Aurora endpoints

Every aurora instance has a specific endpoint, i.e. an URL that identify the host. Those endpoints look like `xxx.yyy.zzz.rds.amazonaws.com`.

There is another endpoint named "cluster endpoint" (format `xxx.cluster-yyy.zzz.rds.amazonaws.com`) which is assigned to the current master instance and will change when a new master is promoted.

In previous version, cluster endpoint use was discouraged, since when a failover occur, this cluster endpoint can point for a limited time to a host that isn't the current master anymore. Old recommandation was to list all specific end-points, like : 

jdbc:mysql:aurora://a.yyy.zzz.rds.amazonaws.com.com,b.yyy.zzz.rds.amazonaws.com.com/db

This kind of url string will still work, but now, recommended url string has to use only cluster endpoint :<br/>

jdbc:mysql:aurora://xxx.cluster-yyy.zzz.rds.amazonaws.com/db

Driver will automatically discover master and slaves of this cluster from current cluster end-point during connection time. This permit to add new replicas to the cluster instance will be discovered without changing driver configuration.

This discovery append at connection time, so if you are using pool framework, check if this framework as a property that controls the maximum lifetime of a connection in the pool, and set a value to avoid infinite lifetime. When this lifetime is reached, pool will discarded the current connection, and create a new one (if needed). New connections will use the new replicas. (If connections are never discarded, new replicas will begin be used only when a failover occur)

Bugfix

  • CONJ-329 and CONJ-330 : rewriteBatchedStatements execute single query exceptions correction.




Changelog

For a list of all changes made in this release, with links to detailed information on each push, see the changelog.

Be notified of new MariaDB Server releases automatically by subscribing to the MariaDB Foundation community announce 'at' lists.mariadb.org announcement list (this is a low traffic, announce-only list). MariaDB plc customers will be notified for all new releases, security issues and critical bug fixes for all MariaDB plc products thanks to the Notification Services.

MariaDB may already be included in your favorite OS distribution. More information can be found on the Distributions which Include MariaDB page.

Comments

Comments loading...
Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.