| Bug #84997 | replication_connection_status does not show file / position | ||
|---|---|---|---|
| Submitted: | 14 Feb 2017 15:29 | Modified: | 30 Mar 2017 6:26 |
| Reporter: | Simon Mudd (OCA) | Email Updates: | |
| Status: | Verified | Impact on me: | |
| Category: | MySQL Server: Replication | Severity: | S4 (Feature request) |
| Version: | 5.7.15 | OS: | Any |
| Assigned to: | CPU Architecture: | Any | |
[14 Feb 2017 15:30]
Simon Mudd
And let us not forget: * master_host / port
[14 Feb 2017 15:31]
Simon Mudd
* and SSL related information
[30 Mar 2017 6:26]
MySQL Verification Team
Hello Simon, Thank you for the report and reasonable feature request! Thanks, Umesh
Description: SELECT from the given table shows some details but does not show file / position attributes. If you do not use GTID it would be convenient to include these settings as a reference to the connection. How to repeat: root@myserver [performance_schema]> select * from replication_connection_status\G *************************** 1. row *************************** CHANNEL_NAME: GROUP_NAME: SOURCE_UUID: 0f123034-fbfa-11e5-b19f-5789b1e4d9a0 THREAD_ID: 10670609 SERVICE_STATE: ON COUNT_RECEIVED_HEARTBEATS: 0 LAST_HEARTBEAT_TIMESTAMP: 0000-00-00 00:00:00 RECEIVED_TRANSACTION_SET: LAST_ERROR_NUMBER: 0 LAST_ERROR_MESSAGE: LAST_ERROR_TIMESTAMP: 0000-00-00 00:00:00 Suggested fix: * Please include file and position information of the I/O thread. * Please also indicate the last time the information (connection status) was updated. It is impossible from this table to see if the connection is busy, or has been idle for some time. * it might be convenient to also include the number of events that have been received. The replication stream consists of a number of events yet none of these (or their counters) are exposed publicly. Adding such information may be useful. All of this is related to bug#84868.