WebDec 18, 2024 · But as I already mentioned I actually want to change the MON’s IP address, not add a new one. So the procedure changes a little: # Change host1 MON's IP address # Cluster still has quorum but looses one MON cephadm:~ # ceph -s cluster: id: 8f279f36-811c-3270-9f9d-58335b1bb9c0 health: HEALTH_WARN 1/3 mons down, quorum … WebCeph was designed from the ground up to deal with the failures of a distributed system. At the next layer, Rook was designed from the ground up to automate recovery of Ceph components that traditionally required admin intervention. ... If you had two mons and one of them went down, you would have 1/2 of quorum. Since that is not a super ...
how to rejoin Mon and mgr Ceph to cluster - Stack Overflow
WebIf a Ceph Monitor has an outdated or corrupted Ceph Monitor map ( monmap ), it cannot join a quorum because it is trying to reach the other Ceph Monitors on incorrect IP … WebMONs can be scaled down via removing existing ceph-mon units. First, you need to make sure the cluster is healthy. To check the cluster health, run: juju ssh ceph-mon/leader … complementary shaders sky is white
Troubleshooting Monitors — Ceph Documentation
WebAug 4, 2024 · Storage backend status (e.g. for Ceph use ceph health in the Rook Ceph toolbox): HEALTH_ERR 1 filesystem is offline; 1 filesystem is online with fewer MDS than max_mds; MDS_ALL_DOWN 1 filesystem is offline; fs myfs is offline because no MDS is active for it. MDS_UP_LESS_THAN_MAX 1 filesystem is online with fewer MDS than … WebSep 3, 2024 · To keep it down, there are 2 ways: - either set "ceph osd set noup", - or actually shut the OSD down. The first version will allow the OSD to keep running so you can talk to the daemon while it is marked "down" . Be aware that the OSD will be marked "out" after a while. You might need to mark it "in" manually when you are done with maintenance. WebAs a reminder here is the list of requirements for production environments: One OCP 4.7 (or greater) cluster. OpenShift Data Foundation (ODF) 4.7 (or greater) Two (2) failure domains for OSD deployment. At least two (2) nodes in each availability zone. LSO is a requirement for UI deployment. complementaryshaders_v4.5.zip