No cache version.

Caching disabled. Default setting for this page:enabled (code DEF204)
If the display is too slow, you can disable the user mode to view the cached version.

Rechercher dans le manuel MySQL

17.1.4.3 Multi-Source Replication Monitoring

Contents

To monitor the status of replication channels the following options exist:

  • Using the replication Performance Schema tables. The first column of these tables is Channel_Name. This enables you to write complex queries based on Channel_Name as a key. See Section 26.12.11, “Performance Schema Replication Tables”.

  • Using SHOW SLAVE STATUS FOR CHANNEL channel. By default, if the FOR CHANNEL channel clause is not used, this statement shows the slave status for all channels with one row per channel. The identifier Channel_name is added as a column in the result set. If a FOR CHANNEL channel clause is provided, the results show the status of only the named replication channel.

Note

The SHOW VARIABLES statement does not work with multiple replication channels. The information that was available through these variables has been migrated to the replication performance tables. Using a SHOW VARIABLES statement in a topology with multiple channels shows the status of only the default channel.

17.1.4.3.1 Monitoring Channels Using Performance Schema Tables

This section explains how to use the replication Performance Schema tables to monitor channels. You can choose to monitor all channels, or a subset of the existing channels.

To monitor the connection status of all channels:

  1. mysql> SELECT * FROM replication_connection_status\G;
  2. *************************** 1. row ***************************
  3. CHANNEL_NAME: master1
  4. GROUP_NAME:
  5. SOURCE_UUID: 046e41f8-a223-11e4-a975-0811960cc264
  6. THREAD_ID: 24
  7. SERVICE_STATE: ON
  8. COUNT_RECEIVED_HEARTBEATS: 0
  9. LAST_HEARTBEAT_TIMESTAMP: 0000-00-00 00:00:00
  10. RECEIVED_TRANSACTION_SET: 046e41f8-a223-11e4-a975-0811960cc264:4-37
  11. LAST_ERROR_NUMBER: 0
  12. LAST_ERROR_MESSAGE:
  13. LAST_ERROR_TIMESTAMP: 0000-00-00 00:00:00
  14. *************************** 2. row ***************************
  15. CHANNEL_NAME: master2
  16. GROUP_NAME:
  17. SOURCE_UUID: 7475e474-a223-11e4-a978-0811960cc264
  18. THREAD_ID: 26
  19. SERVICE_STATE: ON
  20. COUNT_RECEIVED_HEARTBEATS: 0
  21. LAST_HEARTBEAT_TIMESTAMP: 0000-00-00 00:00:00
  22. RECEIVED_TRANSACTION_SET: 7475e474-a223-11e4-a978-0811960cc264:4-6
  23. LAST_ERROR_NUMBER: 0
  24. LAST_ERROR_MESSAGE:
  25. LAST_ERROR_TIMESTAMP: 0000-00-00 00:00:00
  26. 2 rows in set (0.00 sec)

In the above output there are two channels enabled, and as shown by the CHANNEL_NAME field they are called master1 and master2.

The addition of the CHANNEL_NAME field enables you to query the Performance Schema tables for a specific channel. To monitor the connection status of a named channel, use a WHERE CHANNEL_NAME=channel clause:

  1. mysql> SELECT * FROM replication_connection_status WHERE CHANNEL_NAME='master1'\G
  2. *************************** 1. row ***************************
  3. CHANNEL_NAME: master1
  4. GROUP_NAME:
  5. SOURCE_UUID: 046e41f8-a223-11e4-a975-0811960cc264
  6. THREAD_ID: 24
  7. SERVICE_STATE: ON
  8. COUNT_RECEIVED_HEARTBEATS: 0
  9. LAST_HEARTBEAT_TIMESTAMP: 0000-00-00 00:00:00
  10. RECEIVED_TRANSACTION_SET: 046e41f8-a223-11e4-a975-0811960cc264:4-37
  11. LAST_ERROR_NUMBER: 0
  12. LAST_ERROR_MESSAGE:
  13. LAST_ERROR_TIMESTAMP: 0000-00-00 00:00:00
  14. 1 row in set (0.00 sec)

Similarly, the WHERE CHANNEL_NAME=channel clause can be used to monitor the other replication Performance Schema tables for a specific channel. For more information, see Section 26.12.11, “Performance Schema Replication Tables”.


Find a PHP function

Document created the 26/06/2006, last modified the 26/10/2018
Source of the printed document:https://www.gaudry.be/en/mysql-rf-replication-multi-source-monitoring.html

The infobrol is a personal site whose content is my sole responsibility. The text is available under CreativeCommons license (BY-NC-SA). More info on the terms of use and the author.

References

  1. View the html document Language of the document:en Manuel MySQL : https://dev.mysql.com/

These references and links indicate documents consulted during the writing of this page, or which may provide additional information, but the authors of these sources can not be held responsible for the content of this page.
The author This site is solely responsible for the way in which the various concepts, and the freedoms that are taken with the reference works, are presented here. Remember that you must cross multiple source information to reduce the risk of errors.

Contents Haut