Evidence
export-worker accounts for 82% CPU usage. The spike starts at 14:31 with the export batch; memory remains at 54%.
Impact
Export jobs accumulate 240 pending items. Other host processes compete for CPU and take longer to run.
Probable cause
Export batch concurrency saturated CPU: eight workers started together on the same host, according to process metrics and batch logs.
Action
Reduce batch concurrency and monitor CPU and job backlog. Confirm a return to normal before restoring volume.