On Wed, Mar 30, 2016 at 9:27 PM, Adrian Saul
<[email protected]> wrote:
>
>
> It is the monitors that ceph clients/daemons can connect to initially to
> connect with the cluster.
Not quite. The clients will use the "mon initial members" value to
populate their search set, but other config options can fill it as
well ("mon host", for instance). Various setup tools will populate
different ones.
The key to "mon initial members" is that it's used for the initial
cluster assembly. When a monitor turns on for the first time (without
any quorum state), it tries to connect to any other monitors it can
find, and then creates a cluster if nobody else it can find is aware
of one either. But it won't create a cluster if it doesn't get
everybody in mon_initial_members to participate; instead it waits to
talk to them. This isn't a big deal if you're deploying stuff
manually, but is important for some cluster management systems that
automatically populate the cluster information like our original Chef
cookbooks.
-Greg
>
>
>
> Once they connect to one of the initial mons they will get a full list of
> all monitors and be able to connect to any of them to pull updated maps.
>
>
>
>
>
> From: ceph-users [mailto:[email protected]] On Behalf Of
> [email protected]
> Sent: Thursday, 31 March 2016 3:21 PM
> To: [email protected]
> Subject: [ceph-users] Ceph.conf
>
>
>
> Hi,
>
>
>
> What does mean by mon initial members in ceph.conf? Is it monitor node that
> monitor all osd node? Or node osd that been monitor? Care to exlain?
_______________________________________________
ceph-users mailing list
[email protected]
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
