On Tue, Dec 9, 2014 at 3:11 PM, Christopher Armstrong <chris@xxxxxxxxxxxx> wrote: > Hi folks, > > I think we have a bit of confusion around how initial members is used. I > understand that we can specify a single monitor (or a subset of monitors) so > that the cluster can form a quorum when it first comes up. This is how we're > using the setting now - so the cluster can come up with just one monitor, > with the other monitors to follow later. > > However, a Deis user reported that when the monitor in his initial members > list went down, radosgw stopped functioning, even though there are three > mons in his config file. I would think that the radosgw client would connect > to any of the nodes in the config file to get the state of the cluster, and > that the initial members list is only used when the monitors first come up > and are trying to achieve quorum. > > The issue he filed is here: https://github.com/deis/deis/issues/2711 > > He also found this Ceph issue filed: https://github.com/ceph/ceph/pull/1233 Nope, this has nothing to do with it. > > Is that what we're seeing here? Can anyone point us in the right direction? I didn't see the actual conf file posted anywhere to look at, but my guess is simply that (since it looks like you're using generated conf files which can differ across hosts) that the one on the server(s) in question don't have the monitors listed in them. I'm only skimming the code, but from it and my recollection, when a Ceph client starts up it will try to assemble a list of monitors to contact from: 1) the contents of the "mon host" config entry 2) the "mon addr" value in any of the "global", "mon" or "mon.X" sections The clients don't even look at mon_initial_members that I can see, actually — so perhaps your client config only lists the initial monitor, without adding the others? -Greg _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
 |