System News
back1 2 3 4 5 6 7 8 9 10 11 next
Archived MySQL Articles
16 Mar 2017
open to premium members only
MySQL Community Awards 2017: Call for Nominations! [61624]
By Shlomi Noach

Shlomi blogs, "The 2017 MySQL Community Awards event will take place, as usual, in Santa Clara, during the Percona Live Data Performance Conference, April 2017.

The MySQL Community Awards is a community based initiative. The idea is to publicly recognize contributors to the MySQL ecosystem. The entire process of discussing, voting and awarding is controlled by an independent group of community members, typically based of past winners or their representatives, as well as known contributors.

It is a self-appointed, self-declared, self-making-up-the-rules-as-it-goes committee. It is also very aware of the importance of the community; a no-nonsense, non-political, adhering to tradition, self criticizing committee..."
(Get More Information . .)

10 Mar 2017
open to premium members only
Group Replication minimal SQL based configuration [61381]
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
open to premium members only
MySQL Connector/Java 6.0.6-m5 [61382]
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 . .)

07 Mar 2017
open to premium members only
MySQL Cluster Manager 1.4.2 [61394]
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 . .)

04 Mar 2017
open to premium members only
MySQL Enterprise Backup: improved logging messages [61184]
By Rahul Sisondia

Rahul blogs, "Logging is very important diagnostic tool for understanding the behavior of the application as well as troubleshooting any issue with the application. Since MySQL Enterprise Backup (MEB) is a command line application, there is little interaction with the myriad of operations going on behind the scenes. Thus, logging messages is very important in order to know the progress of current operation as well as learning more about errors should they occur. The messages logged by MEB are written to the console and the log file as depicted in the following diagram, which looks similar to the Tee command in UNIX..."
(Get More Information . .)

04 Mar 2017
open to premium members only
Optimistic Incremental Backup [61185]
By Rahul Sisondia

Rahul blogs, "The current incremental backup algorithm scans all the tables to gather changed pages even if very few tables are modified since the previous backup and thus results in a 'full-scan' incremental backup. This may result in increment backups requiring the same amount of time as full backup because it scans all the tables. The new algorithm aims to eliminate this extra time.

The new algorithm scans only those tables that have been modified since the previous backup. This algorithm relies on modification time, which is similar to an earlier improvement made for full backup. That full backup algorithm is known as optimistic full backup, hence new improvement is named 'Optimistic Incremental Backup'. For comparison, we will use optimistic full backup to refer to the performance improvements for full backup and optimistic increment backup for the new improvements to incremental backup..."
(Get More Information . .)

 
back1 2 3 4 5 6 7 8 9 10 11 next