1Z0-888 · Question #45
You are using the Performance Schema to investigate replication on a slave which has a single master. The option slave-parallel-type is set to DATABASE. mysql> SELECT THREAD_ID, threads.NAME…
The correct answer is B. The slave is configured with slave_parallel_workers = 4 E. The slave cannot process the relay log fast enough to use all threads. Four slave worker threads appear in the output (THREAD_IDs 22–25), which directly proves slave_parallel_workers = 4 (B). Workers 22 and 23 show TotalCount = 0, meaning they have never processed a single event since replication started - with all instruments enabled and threads…
Question
Options
- AThe salve has two intermediate relay slaves connected to it.
- BThe slave is configured with slave_parallel_workers = 4
- CAt most, two schemas are being updates concurrently.
- DTHREAD_ID 21 has stopped running.
- EThe slave cannot process the relay log fast enough to use all threads.
- FThe server needs more cores to use all slave threads.
How the community answered
(35 responses)- A20% (7)
- B63% (22)
- C3% (1)
- D3% (1)
- F11% (4)
Explanation
Four slave worker threads appear in the output (THREAD_IDs 22–25), which directly proves slave_parallel_workers = 4 (B). Workers 22 and 23 show TotalCount = 0, meaning they have never processed a single event since replication started - with all instruments enabled and threads instrumented, the only explanation is that the relay log isn't arriving fast enough to dispatch work to all four workers, confirming E.
Why the distractors are wrong:
- A - Intermediate relay slaves would show additional
slave_ioandslave_sqlthreads, not extraslave_workerthreads; none appear here. - C - The zero counts on workers 22/23 reflect a relay log throughput bottleneck, not a hard limit on schemas; you cannot infer a schema count from idle workers.
- D - Thread 21 (
slave_sql) hasTotalCount = 3875, so it has processed events and is running as the coordinator thread. - F - The bottleneck is relay log I/O speed (the I/O thread can't feed events fast enough), not CPU core count; more cores wouldn't fix an I/O-bound problem.
Memory tip: Think "4 workers listed = slave_parallel_workers=4; zero-count workers = starved workers = relay log can't keep up." The Performance Schema never lies about what has run - a count of 0 with all instruments enabled means that thread has genuinely never been used.
Topics
Community Discussion
No community discussion yet for this question.