Re: Client behavior when adding and removing mons

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 31/07/17 14:05, Edward R Huyer wrote:
> I’m migrating my Ceph cluster to entirely new hardware.  Part of that is replacing the monitors.  My plan is to add new monitors and remove old ones, updating config files on client machines as I go.
> 
> I have clients actively using the cluster.  They are all QEMU/libvirt and kernel clients using RBDs.  Will they continue to function correctly as long as I update the applicable config files with new monitor info?  Or will I need to restart the VMs and remap the RBDs on the physical boxes?
> 
> I **think** the clients keep an updated list of the current active monitors while the clients are running, but I’m not positive.  Hopefully someone knows definitively.
> 
> Thanks in advance!
> 
> -----
> 
> Edward Huyer

The monitor list specified in the config file is an "initial set" the client/daemons use to establish first contact with the cluster. Once they've been able to communicate with a monitor successfully, they thereafter use the provided monmap to keep track of monitors and the config file is irrelevant - so as long as you keep a quorum of monitors online at all times, you shouldn't have any issues with running clients. I did an OS/hardware upgrade recently and spun up temporary monitors on normally non-mon nodes to keep the cluster online while I was working on the regular hosts, and no restarting of clients was required.

Rich

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com

[Index of Archives]     [Information on CEPH]     [Linux Filesystem Development]     [Ceph Development]     [Ceph Large]     [Ceph Dev]     [Linux USB Development]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [xfs]


  Powered by Linux