I guess I should add, what if I add OSDs to a mon in this scenario? Do they get up and in and will the crush map from the non initial mons get merged with the initial when it's online? > -----Original Message----- > From: ceph-users-bounces@xxxxxxxxxxxxxx [mailto:ceph-users- > bounces@xxxxxxxxxxxxxx] On Behalf Of Don Talton (dotalton) > Sent: Friday, December 20, 2013 9:17 AM > To: Gregory Farnum > Cc: ceph-users@xxxxxxxxxxxxxx > Subject: Re: ceph-deploy issues with initial mons that aren't up > > This makes sense. So if other mons come up that are *not* defined as initial > mons, then they will not be in service until the initial mon is up and ready? At > which point they can form their quorum and operate? > > > > -----Original Message----- > > From: Gregory Farnum [mailto:greg@xxxxxxxxxxx] > > Sent: Thursday, December 19, 2013 10:19 PM > > To: Don Talton (dotalton) > > Cc: ceph-users@xxxxxxxxxxxxxx > > Subject: Re: ceph-deploy issues with initial mons that > > aren't up > > > > "mon initial members" is a race prevention mechanism whose purpose is > > to prevent your monitors from forming separate quorums when they're > > brought up by automated software provisioning systems (by not allowing > > monitors to form a quorum unless everybody in the list is a member). > > If you want to add other monitors at a later time you can do so by > > specifying them elsewhere (including in mon hosts or whatever, so > > other daemons will attempt to contact them.) -Greg Software Engineer > > #42 @ http://inktank.com | http://ceph.com > > > > > > On Thu, Dec 19, 2013 at 9:13 PM, Don Talton (dotalton) > > <dotalton@xxxxxxxxx> wrote: > > > I just realized my email is not clear. If the first mon is up and > > > the additional > > initials are not, then the process fails. > > > > > >> -----Original Message----- > > >> From: ceph-users-bounces@xxxxxxxxxxxxxx [mailto:ceph-users- > > >> bounces@xxxxxxxxxxxxxx] On Behalf Of Don Talton (dotalton) > > >> Sent: Thursday, December 19, 2013 2:44 PM > > >> To: ceph-users@xxxxxxxxxxxxxx > > >> Subject: ceph-deploy issues with initial mons that > > >> aren't up > > >> > > >> Hi all, > > >> > > >> I've been working in some ceph-deploy automation and think I've > > >> stumbled on an interesting behavior. I create a new cluster, and > > >> specify 3 machines. If all 3 are not and unable to be ssh'd into > > >> with the account I created for ceph- deploy, then the mon create > > >> process will fail and the cluster is not properly setup with keys, etc. > > >> > > >> This seems odd to me, since I may want to specify initial mons that > > >> may not yet be up (say they are waiting for cobbler to finish > > >> loading them for example), but I want them as part of the initial cluster. > > >> > > >> > > >> Donald Talton > > >> Cloud Systems Development > > >> Cisco Systems > > >> > > >> > > >> > > >> _______________________________________________ > > >> ceph-users mailing list > > >> ceph-users@xxxxxxxxxxxxxx > > >> http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com > > > _______________________________________________ > > > ceph-users mailing list > > > ceph-users@xxxxxxxxxxxxxx > > > http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com > _______________________________________________ > ceph-users mailing list > ceph-users@xxxxxxxxxxxxxx > http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
 |