MySQL Bugs: #82625: destroy_mysql_connection should use cnx.disconnect instead of cnx.shutdown

Bug #82625	destroy_mysql_connection should use cnx.disconnect instead of cnx.shutdown
Submitted:	18 Aug 2016 6:57
Reporter:	Tsubasa Tanaka (OCA)	Email Updates:
Status:	Won't fix	Impact on me:	None
Category:	MySQL Fabric	Severity:	S3 (Non-critical)
Version:	1.5.6	OS:	Any
Assigned to:		CPU Architecture:	Any

Description:
MySQL Fabric uses cnx.shutdown in _server_utils.destroy_mysql_connection.

https://github.com/mysql/mysql-fabric/blob/release-1.5.6/lib/mysql/fabric/server_utils.py#...

But shutdown() quits without COM_QUIT packet, this causes error-log entries at mysqlds in Farm each time of calling MySQLServer.is_alive.

```
2016-08-03T09:53:49.127538+09:00 86612 [Note] Aborted connection 86612 to db: 'unconnected' user: 'fabric' host: '<fabric_host>' (Got an error reading communication packets)
```

https://dev.mysql.com/doc/connector-python/en/connector-python-api-mysqlconnection-shutdow...

How to repeat:
Setup MySQL Fabric and `group create`, `group add`, `group activate` and see mysqld(not backing-store)'s error-log.

Suggested fix:
Use cnx.disconnect instead of cnx.shutdown.

https://github.com/gmo-media/mikasafabric/commit/bf4d3ab54720295fad7bab6f396133c956d75187

Status updated to 'Won't fix' (Fabric is now covered under Oracle Lifetime Sustaining Support)