Bug #2436
closedmon: suicides when trying to join an existing quorum
0%
Description
I have mon.single running happily at 192.168.122.91. On 192.168.122.159, I run (using the right values for key and fsid):
monmaptool --create --clobber --add single 192.168.122.91 --add blahblah 192.168.122.159 monmap.tmp
echo -e '[mon.]\nkey = AQARQqhPCENjJBAAKW0xeZy4auqW1YNKSfOjNw==' >keyring.tmp
sudo ceph-mon --mkfs -i blahblah --fsid=07535b46-8429-4efd-9b2d-6b1170752448 --monmap=monmap.tmp --keyring=keyring.tmp
sudo /usr/bin/ceph-mon --cluster=ceph -i blahblah -f
and it fails with
2012-05-16 14:47:49.433136 7fc005f087a0 0 ceph version 0.46-219-g34d5582 (commit:34d558259481ff21f2eb30053ceb15e3992074f1), process ceph-mon, pid 3632
2012-05-16 14:47:49.434371 7fc005f087a0 1 mon.blahblah@1(probing) e0 init fsid 07535b46-8429-4efd-9b2d-6b1170752448
2012-05-16 14:47:49.438444 7fc001012700 0 mon.blahblah@1(probing) e1 removed from monmap, suicide.
Updated by Greg Farnum almost 12 years ago
This is because when you provide a new monitor with a monmap that includes both itself and existing monitors, the new mon disagrees on whether or not it's an established member of the cluster.
There are approximately a million ways in which what you're trying to do here won't and can't work without some sort of signal that it's a new mon, which it respects and handles appropriately. We'll need to talk about the right design for something like that.
Updated by Sage Weil almost 12 years ago
- Status changed from New to Resolved