Database is currently being compacted error in database writer component

Goal: Determine whether the "database is currently being compacted" error observed in the database writer component leads to measurable write latency increases under concurrent load.

Constraints: The error may appear only when compaction contends for disk I/O and file descriptors, and its impact varies with automatic versus manual compaction scheduling and across CouchDB 3.x versions where stats names and defaults differ.

Uncertainty: It is unclear what latency threshold constitutes an unacceptable spike, how to isolate compaction‑induced queuing from other I/O bottlenecks, and whether automatic compaction should be throttled or disabled during sustained write workloads.

Questions: What latency increase signals problematic compaction contention? How can administrators distinguish compaction‑related queuing from general disk saturation? Should automatic compaction be adjusted based on real‑time I/O headroom?