Network & Infrastructure / Storage Networks & Distributed Data
Ceph slow operations: storage latency or network delay
Clients report slow I/O while the cluster remains available. A slow-operation warning can reflect disk, network, CPU or a dependency between these resources rather than one universal failure.
Environment and inputs: Ceph and storage transport dependencies; match health identifiers and recovery behavior to the installed release. Diagnostic/design example; not tested on production equipment.
Collect the evidence
Correlate health detail, affected OSDs, operation timing, device latency and network counters over the same interval. Compare whether slow operations concentrate on one host, device class or network path.
Explain the result
A warning identifies delayed work, not necessarily the component that caused it. Shared timing across unrelated disks can point toward host or network contention instead of simultaneous device failure.
Plan the fix
Repair the demonstrated dependency and review the release-specific health guidance. Avoid restarting every slow OSD before preserving evidence or assessing the recovery load that a restart creates.
Check the result and rollback
Measure client latency and slow-operation recurrence under comparable workload. Revert a tuning change if it only suppresses warnings or increases recovery pressure without improving completed I/O.