Network & Infrastructure / Storage Networks & Distributed Data
Inactive placement groups versus ordinary degraded redundancy
An application loses I/O to part of a pool while the cluster dashboard highlights many health warnings. Inactive placement groups have a different service implication from merely degraded protection.
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
Inspect placement-group states, affected objects, acting sets and relevant OSD availability. Prioritize availability-blocking conditions separately from warnings that report reduced redundancy but permit I/O.
Explain the result
Health severity and state names describe different mechanisms. A degraded state does not automatically imply unavailable data, while an inactive group can directly block access to its contents.
Plan the fix
Use the installed release's state-specific recovery guidance and preserve data-bearing devices. Avoid force operations or deleting objects merely to make a health summary look cleaner.
Check the result and rollback
Verify affected application data becomes accessible and protection restores through supported recovery. Halt changes if an operation risks discarding the only authoritative copy or obscures which devices hold required data.