System News
MySQL
10 Mar 2017
#61381
Group Replication minimal SQL based configuration
By Andrew Grimo

Andrew Grimo blogs, "So you're interested in the 'new' MySQL Group Replication feature but are concerned that configuring it is going to be difficult. Let me soothe those concerns with this blog post. Yes, the MySQL team has recently been discussing other methods to configure Group Replication using the RC release of MySQL Shell and how it can be used for tools such as Puppet for enhanced provisioning of a Group as Lefred has demonstrated in his MySQL Puppet post.

To start, I'll post a sample my.cnf file below and highlight the related configurations that Group Replication requires. Yes, there are a number of them. I'll try and lay that out below so it is easy to follow. But first..."
(Get More Information . .)

10 Mar 2017
#61382
MySQL Connector/Java 6.0.6-m5
By MySQL Release Engineering

"Dear MySQL users,

MySQL Connector/J 6.0.6 m5 Development Release is a developer milestone release for the 6.0.x series.

This release includes the following new features and changes, also described in more detail here

As always, we recommend that you check the "CHANGES" file in the download archive to be aware of changes in behavior that might affect your application.

To download MySQL Connector/J 6.0.6 m5, see the "Development Releases" tab here

Enjoy!"
(Get More Information . .)

7 Mar 2017
#61394
MySQL Cluster Manager 1.4.2
By Thomas Nielsen, March 7th, 2017

Thomas blogs, "In this blog post we will highlight some of the details of the MCM 1.4.2 release.

Progress reporting

First, some eye candy. With MCM 1.4.2 we added simple progress reporting. There is now a simple way to get some sense of progress, especially interesting for long-running commands. There is a plain variant, and one which includes an ascii-art progressbar.

Combine this with something like the linux/unix watch command, and you can easily monitor cluster health directly in the CLI. Please note that monitoring using a very short timer, combined with a log-level of debug/info, will cause excessive logging..."
(Get More Information . .)

See all archived MySQL articles See all articles from this issue