The Ultimate Guide to High Availability with MariaDB

MariaDB Connector/J 1.3.4 Release Notes

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

Download Release Notes Changelog Connector/J Overview

Release date: 11 Jan 2016

MariaDB Connector/J 1.3.4 is a Stable (GA) release.

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

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

This version is a bugfix release

Notable changes and additions

Major

  • Failover improvements (reconnection implementation evolution, thread handling ...)
  • CONJ-236 : Correction on using getInt on a signed smallInt negative value on prepareStatement
  • CONJ-238 : PrepareStatement prepare exception handling

Minor

  • CONJ-237 : Closing a close statement does not throw an Exception anymore
  • CONJ-239 : Permit commit when in autocommit mode
  • CONJ-240 : Permit using Connection.setReadOnly(true) during a transaction

Behavior change

On a master/slave cluster, driver use underlying 2 connections: one to a master instance, one to a slave instance. When one of the connection fail, if driver does need it at once, it will create a new connection immediately before re-executing query if possible.

If the failed connection is not needed immediately, this driver will subscribe to the "failover reconnection" that will be handle in other threads. Failover threads will attempt to create new connection to replace failing ones, so the interruption is minimal for the queries in progress. When client asked to use a failed connection, the new connection created by failover thread will replace the failed one.

Example: after a failure on a slave connection, readonly operations are temporary executed on the master connection to avoid interruption client side. Failover thread will then create a new slave connection that will replace the failed one. Next query will use the new slave connection.

A pool of threads is initialized when using a master/slave configuration. The pool size evolves according to the number of connection.

more informations on high availability documentation

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.