Bug #74765 | RPL P_S: move SQL thread status to worker table | ||
---|---|---|---|
Submitted: | 10 Nov 2014 12:54 | Modified: | 16 Sep 2015 8:52 |
Reporter: | Shivji Jha | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Replication | Severity: | S3 (Non-critical) |
Version: | 5.7.2 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[10 Nov 2014 12:54]
Shivji Jha
[16 Sep 2015 8:52]
Jon Stephens
Documented the feature change in the 5.7.9 and 5.8.0 changelogs, as follows: When using a single-threaded slave, the status of the applier thread is now reported as part of the replication_applier_status_by_worker table, instead of replication_applier_status_by_coordinator. This means that replication_applier_status_by_coordinator is now empty when using a single-threaded slave; it should be noted that such reporting for multi-threaded slaves has not been changed, and continues to be shown in this table. Also updated the descriptions of these tables in the Manual. Closed.