Bug #76637 replication_applier_status_by_worker shows wrong worker_id when slave stops.
Submitted: 9 Apr 2015 10:18 Modified: 16 Jul 2015 12:29
Reporter: Libing Song Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Replication Severity:S3 (Non-critical)
Version:5.7 OS:Any
Assigned to: CPU Architecture:Any

[9 Apr 2015 10:18] Libing Song
Description:
replication_applier_status_by_worker shows wrong worker_id when slave stops.
all worker_ids are 1.

How to repeat:
--source include/master-slave.inc

--connection slave
--source include/stop_slave_sql.inc
SET GLOBAL slave_parallel_workers = 4;
--source include/start_slave_sql.inc
--source include/stop_slave_sql.inc

select * from performance_schema.replication_applier_status_by_worker;
[16 Jul 2015 12:29] David Moss
The following was noted in the 5.7.8 changelog:
When a slave was stopped, replication_applier_status_by_worker showed worker_id as 1 and did not show the correct number.