Questo contenuto non è disponibile nella lingua selezionata.
Chapter 9. Troubleshooting clusters in stretch mode
You can replace and remove the failed tiebreaker monitors. You can also force the cluster into the recovery or healthy mode if needed.
9.1. Forcing stretch cluster into recovery or healthy mode Copia collegamentoCollegamento copiato negli appunti!
When in stretch degraded mode, the cluster goes into the recovery mode automatically after the disconnected data center comes back. If that does not happen, or you want to enable recovery mode early, you can force the stretch cluster into the recovery mode.
Prerequisites
- A running Red Hat Ceph Storage cluster
- Stretch mode in enabled on a cluster
Procedure
Force the stretch cluster into the recovery mode:
Example
[ceph: root@host01 /]# ceph osd force_recovery_stretch_mode --yes-i-really-mean-it
[ceph: root@host01 /]# ceph osd force_recovery_stretch_mode --yes-i-really-mean-itCopy to Clipboard Copied! Toggle word wrap Toggle overflow NoteThe recovery state puts the cluster in the
HEALTH_WARNstate.When in recovery mode, the cluster should go back into normal stretch mode after the placement groups are healthy. If that does not happen, you can force the stretch cluster into the healthy mode:
Example
[ceph: root@host01 /]# ceph osd force_healthy_stretch_mode --yes-i-really-mean-it
[ceph: root@host01 /]# ceph osd force_healthy_stretch_mode --yes-i-really-mean-itCopy to Clipboard Copied! Toggle word wrap Toggle overflow NoteYou can also run this command if you want to force the cross-data-center peering early and you are willing to risk data downtime, or you have verified separately that all the placement groups can peer, even if they are not fully recovered.
You might also wish to invoke the healthy mode to remove the
HEALTH_WARNstate, which is generated by the recovery state.NoteThe
force_recovery_stretch_modeandforce_recovery_healthy_modecommands should not be necessary, as they are included in the process of managing unanticipated situations.