Friday, March 3, 2017

WatchDog for MySQL Group Replication Servers

MySQL Group Replication has been released since MySQL 5.7.17.
A quick start guide can be on the following URL

If there is a network partition between a group of Servers, it may introduce arbitration to find out and determine the next action for the Group of the Servers.
For documentation about Network Partitioning with Group Replication, please refer to the following URL::

This blog is written to introduce my 'demo' version of arbitrator / watchdog.   From here onwards, I refer this arbitrator as gr_watchdog.
Another public arbitrator from Matt Lord can also be found on :
As an example, an application connecting to a group of servers with 5 MySQL instances on 2 machines.   Machine 1 (S1, S2, S3) and Machine 2 (S4, S5)

The following table is an example of the configuration for the Group Replication.
Group Setting
Basic Server Configuration datadir=…
S1: port=3306
S2: port=3316
S3: port=3326
S4: port=3306
S5: port=3316
socket=<socket file not to be same as other on the same machine>
Replication Configuration log-bin
Group Replication Configuration plugin-load
= 8a94f357-aab4-11df-86ab-c80aa9429562
S1 : group_replication_local_address=primary:4306
S2:  group_replication_local_address=primary:4316
S3: group_replication_local_address=primary:4326
S4: group_replication_local_address=secondary:4306
S5: group_replication_local_address=secondary:4306
group_replication_group_seeds =primary:4306,primary:4316,primary:4326,secondary:4306,secondary:4316

The 5 servers are all connected as Group Replication thru INTERNAL Network Interface. 
The setting below tells each of the member server to connect to “interface:port”.   “primary|secondary” on the machine can be the interface to INTERNAL Network dedicated for Group Replication.  
S1 : group_replication_local_address=primary:4306
S2:  group_replication_local_address=primary:4316
S3: group_replication_local_address=primary:4326
S4: group_replication_local_address=secondary:4306
S5: group_replication_local_address=secondary:4306

group_replication_group_seeds =primary:4306,primary:4316,primary:4326,secondary:4306,secondary:4316

Application connecting to the MySQL Servers is  going thru another Network Interface.  MySQL Router is used as the routing between MySQL Servers and the Application(s).

When the 5 MySQL Servers are up and running with the Group Replication, the member status can be checked using the following SQL statement on Performance_Schema
mysql> SELECT * FROM performance_schema.replication_group_members;
The following screenshot shows the 5 MySQL Instances running on 2 machines (virtual-23, virtual-24).  Given that the virtual-23 has 3 MySQL Instances and virtual-24 has 2 MySQL Instances.  They are all running with ONLINE state.

If there is any problem to the INTERVAL Network Interface between the 2 machines.   MySQL Instances (S1-S2-S3) is separated from (S4-S5).
It forms 2 group of Servers which they are disjointed.

 On the Majority Group with the Machine 1 (virtual-23), all three Server S1-S2-S3 are connected as ONLINE.   The size of the group becomes 3.
Where as On the Machine 2 (virtual-24), the Group Size is still 5 but only the 2 servers are ONLINE.   The size of 2 is a minority with regards to the Group Size as 5.   

The above diagram shows the Member State of Machine1:virtual-23 on the Left Side.  The Member State of Machine2:virtual-24 on the Right Side.
Machine1:virtual-23 has 3 ONLINE members in the Group. 
Machine2:virtual-24 has 2 ONLINE members out of the 5 member size in the Group.   3 members are marked as UNREACHABLE. 
Application if connected to this minority group (S4-S5) Servers may have uncertainty with data.  Updating data is prohibited by the nature of the Group Replication Architecture.

The gr_watchdog is shared as illustration to detect the member state in the group and take action (SHUTDOWN | READONLY | RESTARTGR) on the server(s).

A script “” is created to monitor the local MySQL Servers on the machine.

The monitor each of the MySQL Server Instances on the machine by using the
--login-path  which is created by mysql_config_editor.
For details about the “mysql_config_editor”, refer to the documentation :

A stored function “gr_is_major_online_member()” as show below :
delimiter //
use sys//
drop function if exists gr_is_major_online_member//
create function gr_is_major_online_member()
        returns boolean NOT DETERMINISTIC
        DECLARE li_row INT DEFAULT 0;
        SELECT IF( MEMBER_STATE='ONLINE' AND   ((SELECT COUNT(*) FROM performance_schema.replication_group_members
                WHERE MEMBER_STATE != 'ONLINE') >=  ((SELECT COUNT(*) FROM performance_schema.replication_group_members)/2) = 0), 1, 0 )
                INTO li_row   FROM performance_schema.replication_group_members JOIN performance_schema.replication_group_member_stats USING(member_id);
        IF li_row = 1 THEN
        END IF;

If MySQL servers are in a Group Replication and they are all connected, executing the stored function creation on any of the server instance will be able to install the Stored Function to all server instances.

The contains the configuration settings.
export MYSQL_HOME=/usr/local/mysql
Provide the MYSQL HOME installation
Add to the PATH
# ACTION if there is any failure
 SHUTDOWN – shutdown using mysqladmin
READONLY – issue set READ_ONLY and SUPER_READ_ONLY on the server
 RESTARTGR – issue “stop group_replication;” and start group_replication;” to restart the Group Replication
export RETRY_COUNT=3
In case of Server Failed in the Group (Not online or not in majority group), the retry count determine the number of retry before ACTION is taken
export QUIET_MODE=0
INFO logging if QUIET_MODE=0
export GRSERVERS=gr3306:gr3316:gr3326
The member servers to be checked.  It is based on the
--login-path from the mysql_config_editor. 
Format :login-path[:login-path]…
export GRINTERVAL=30
Polling interval
export OUTDIR=/home/mysql/demo/GroupReplication/grwatchdog/log
Output directory (privilege to “WRITE and CREATE” file(s)

# start

# stop
kill the process

To illustrate the gr_watchdog for the ACTION=READONLY; while ALL member servers are running, issue “stop group_replication;” on one of the server.   After retrying up to RETRY_COUNT=3, the server is set to READ ONLY – including READ_ONLY and SUPER_READ_ONLY.  

To enable the GROUP REPLICATION, be sure to disable the READ_ONLY and SUPER_READ_ONLY if the “group_replication_single_primary_mode” is not set to TRUE.

You can download the grwatchdog.tar from the following LINK 
Any comment, appreciate your sharing!!!    

Again, the is just a demonstration how we can create external arbitrator / watchdog for MySQL Group Replication Servers.

Friday, June 10, 2016

Python App connecting to MySQL with mysql.connector + Failover

The following is the very basic Python App connecting to MySQL Database. (
It connects to the MySQL Database ( with root and empty password). 
import mysql.connector
import sys

if len(sys.argv) > 1 :
        _pass = sys.argv[1]
else :
        _pass = ''
cnx = mysql.connector.connect(user='root', password=_pass, host='', port=3306, database='mysql')


The alternative using Python Dictionary parameter -

This can be useful way to connect to MySQL Database with named parameters. (
import mysql.connector
import sys

_pass = ''
if len(sys.argv) > 1 :
        _pass = sys.argv[1]

config = {
        'user': 'root',
        'password': _pass,
        'host': '',
        'database': 'mysql',
        'raise_on_warnings': True,

cnx = mysql.connector.connect(**config)

Error Handling with MySQL  (
The following example shows the connection to the default db ("test") with using root empty password user.    The error handling processing using try/except/else together with mysql.connector.errorcode.  By providing first argument with invalid password, the python app will get  exception - "errorcode.ER_ACCESS_DENIED_ERROR".  Whereas by giving 2nd argument with a non-exists database, the python app will generate exception "errorcode.ER_BAD_DB_ERROR".

import mysql.connector
from mysql.connector import errorcode
import sys

if len(sys.argv) > 1 :
        _pass = sys.argv[1]
if len(sys.argv) > 2 :
        _db = sys.argv[2]

  cnx = mysql.connector.connect(user='root', host='', port=3306,

  print("connect success")
except mysql.connector.Error as err:
  if err.errno == errorcode.ER_ACCESS_DENIED_ERROR:
       print("Something is wrong with your user name or password")
  elif err.errno == errorcode.ER_BAD_DB_ERROR:
       print("Database does not exist")
  print ("Finally - close connection")
Lastly,  mysql.connector provides connection property "failover".
Please find more details on

The following sample ( provides a sample to connect to databases (3306 and 3316).  If 3306 is stopped, the connection goes to the 3316. 

import mysql.connector
from mysql.connector import errorcode

DB_NAME = 'mysql'

operation = 'SELECT @@hostname, @@port'

config = {
        'raise_on_warnings': True,
        'failover' : [{
                'user': 'root',
                'password': '',
                'host': '',
                'port': 3306,
                'database': 'mysql',
                }, {
                'user': 'root',
                'password': '',
                'host': '',
                'port': 3316,
                'database': 'mysql',
cnx = mysql.connector.connect(**config)

cursor = cnx.cursor()

  for result in cursor.execute(operation, multi=True):
     if result.with_rows:
        print("rows producted by statement '{}':".format(result.statement))
        row = cursor.fetchone()
        while row:
           row = cursor.fetchone()
        print("Number of rows affeted by statement '{}':{}".format(result.statement, result.rowcount))
except mysql.connector.Error as err:


Tuesday, April 5, 2016

Running SYS Schema - "diagnostics" to get insight of your MySQL Database

You may want to dump diagnostic information about the running MySQL Database.  
For MySQL 5.7, the SYS schema comes with the installation.  You can find the corresponding information on

For MySQL 5.6,the SYS schema can be downloaded from the following URL

The zip file as ‘’ is expanded, where the sys_56.sql can be loaded into the MySQL 5.6 database.

# mysql -uroot -h127.0.0.1 < sys_56.sql

Using MySQL Workbench and connecting to the Server, you can find the SYS schema installed.

Running the “diagnostics” stored procedure :
                Parameter :
120 : the max execution time for diagnostics
30 :  The interval time for output
current : The mode of diagnostics information
mysql > tee output.txt;
mysql > call sys.diagnostics (120, 30, ‘current’);
mysql > tee off;

The following section gives you a brief about this diagnostic output.

Part I : The System Environment and Configuration
It shows the basic information about the OS and the MySQL Server.  
| Name                    | Value                                                   |
| Hostname                | virtual-21.localhost                                    |
| Port                    | 3306                                                    |
| Socket                  | /var/lib/mysql/data/EE/EE.sock                          |
| Datadir                 | /var/lib/mysql/data/EE/data1/                           |
| Server UUID             | e0a37616-a942-11e5-9d3f-080027dbc0db                    |
| ----------------------- | ------------------------------------------------------- |
| MySQL Version           | 5.6.24-enterprise-commercial-advanced-log               |
| Sys Schema Version      | 1.5.0                                                   |
| Version Comment         | MySQL Enterprise Server - Advanced Edition (Commercial) |
| Version Compile OS      | linux-glibc2.5                                          |
| Version Compile Machine | x86_64                                                  |
| ----------------------- | ------------------------------------------------------- |
| UTC Time                | 2015-12-23 08:39:01                                     |
| Local Time              | 2015-12-23 16:39:01                                     |
| Time Zone               | SYSTEM                                                  |
| System Time Zone        | HKT                                                     |
| Time Zone Offset        | 08:00:00                                                |
17 rows in set (0.01 sec)

The Configuration part has the Global Variables listing at the time of the execution.
| Variable_name                                          | value                           |
| autocommit                                             | ON                              |
| automatic_sp_privileges                                | ON                              |
| wait_timeout                                           | 28800                           |
444 rows in set (0.02 sec)

Part II : The Performance Schema Info

Listing about what has been setup about Performance Schema (Actors, Consumers, Instruments, Objects, Threads)

Part III : Replication Status
For my case, it is empty.
| Replication Status        |
| No Replication Configured |
1 row in set (0.05 sec)

Part IV – For each Iteration, the following list of information will be printed out to the output file.  (in my case, each iteration is about 30 seconds interval until 120seconds max time)

| NOW()               | The following output is: |
| 2015-12-23 16:39:01 | Iteration Number 1       |
1 row in set (0.34 sec)

| The following output is: |
1 row in set (0.34 sec)

| File                      | Position | Binlog_Do_DB | Binlog_Ignore_DB | Executed_Gtid_Set                          |
| myreplication1-bin.000004 |      191 |              |                  | e0a37616-a942-11e5-9d3f-080027dbc0db:1-416 |
The Show Engine InnoDB status, Transaction, and process list are listed.
The details is not discussed in this blog.

Part V – End of execution, the following information is captured and compared.

a.   The performance schema status
b.   The Schema Information
| Total Number of Tables |
|                    231 |
1 row in set (1 min 30.56 sec)

c.   The Overall Status
a.   Performance Schema Statement Digest Average Latency Histogram
  . = 1 unit
  * = 2 units
  # = 3 units

(0 - 5729ms)      321 | ###########################################################################################################
(5729 - 11458ms)  0   |
(11458 - 17187ms) 1   | .
(17187 - 22916ms) 0   |
(22916 - 28645ms) 0   |
(28645 - 34374ms) 0   |
(34374 - 40104ms) 0   |
(40104 - 45833ms) 0   |
(45833 - 51562ms) 0   |
(51562 - 57291ms) 0   |
(57291 - 63020ms) 1   | .
(63020 - 68749ms) 0   |
(68749 - 74478ms) 1   | .
(74478 - 80207ms) 0   |
(80207 - 85936ms) 0   |
(85936 - 91665ms) 0   |

  Total Statements: 325; Buckets: 16; Bucket Size: 5729 ms;
1 row in set (1 min 30.64 sec)

There are some configuration values for the diagnostics - sys.sys_config as shown :

‘diagnostics.allow_i_s_tables’  - ON/OFF, if ON, the information schema about the tables information will be dumped. 
‘diagnostics.include_raw’ – ON/OFF, if ON, the raw information will be included.