Hello all,
We have been successfully running a 5-node ceph nautilus cluster for a while, on Proxmox 6.4. We have unfortunately undergone a serious power failure which crashed the ceph, 5 of the 27 osds being ejected from the cluster. These could only be reinserted after having been destroyed and re-created.
Ceph has since then been reconstructing.
However, the ceph cluster has become completely unresponsive after the 3 monitors became full. I noticed /var/log/ceph/ceph.log was huge on the 3 monitors, deleting this file solved the issue and got the ceph running again (still reconstructing).
The ceph has again become unresponsive, this time because of the monitor db inflating at an alarming rate. I tried the command
but nothing happened (the command did not complete and was aborted).
I destroyed and recreated the monitor having the issue, leaving the 2 others running. The monitor got destroyed, space available was recovered. As soon as it was restarted, store.db has inflated again to fill up the entire / partition in a couple of minutes.
Any suggestion as to how to solve this?
Thanks
We have been successfully running a 5-node ceph nautilus cluster for a while, on Proxmox 6.4. We have unfortunately undergone a serious power failure which crashed the ceph, 5 of the 27 osds being ejected from the cluster. These could only be reinserted after having been destroyed and re-created.
Ceph has since then been reconstructing.
However, the ceph cluster has become completely unresponsive after the 3 monitors became full. I noticed /var/log/ceph/ceph.log was huge on the 3 monitors, deleting this file solved the issue and got the ceph running again (still reconstructing).
The ceph has again become unresponsive, this time because of the monitor db inflating at an alarming rate. I tried the command
Bash:
ceph tell mon.prox5 compact
I destroyed and recreated the monitor having the issue, leaving the 2 others running. The monitor got destroyed, space available was recovered. As soon as it was restarted, store.db has inflated again to fill up the entire / partition in a couple of minutes.
Any suggestion as to how to solve this?
Thanks
Last edited: