Hello,
I'm running a ceph-12.2.2 cluster on debian/stretch with three mon
servers, unsuccessfully trying to add another (or two additional) mon
servers. While the new mon server keeps in state "synchronizing", the
old mon servers get out of quorum, endlessly changing state from "peon"
to "electing
Hello,
thank you very much for the hint, you are right!
Kind regards, Thomas
Marc Roos schrieb am 30.08.2017 um 14:26:
>
> I had this also once. If you update all nodes and then systemctl restart
> 'ceph-osd@*' on all nodes, you should be fine. But first the monitors of
> course
Hello,
when I upgraded (yet a single osd node) from v12.1.0 -> v12.2.0 its osds
start flapping and finally got all marked as down.
As far as I can see, this is due to an incompatibility of the osd
heartbeat protocol between the two versions:
v12.2.0 node:
7f4f7b6e6700 -1 osd.X 3879 heartbeat_che
Hello,
Thomas Gebhardt schrieb am 07.07.2017 um 17:21:
> ( e.g.,
> ceph-deploy osd create --bluestore --block-db=/dev/nvme0bnp1 node1:/dev/sdi
> )
just noticed that there was typo in the block-db device name
(/dev/nvme0bnp1 -> /dev/nvme0n1p1). After fixing that misspelling my
coo
Hello,
just testing the latest luminous rc packages on debian stretch with
bluestore OSDs.
OSDs without a separate block.db partition do fine.
But when I try to create an OSD with a separate block.db partition:
( e.g.,
ceph-deploy osd create --bluestore --block-db=/dev/nvme0bnp1 node1:/dev/sdi
