No, you definitely don't need to shut down the whole cluster. Just do a polite shutdown of the daemons, optionally with the noout flag that Wido mentioned. Software Engineer #42 @ http://inktank.com | http://ceph.com
On Thu, Jun 19, 2014 at 1:55 PM, Alphe Salas Michels <asa...@kepler.cl> wrote: > Hello, the best practice is to simply shut down the whole cluster starting > form the clients, monitors the mds and the osd. You do your maintenance > then you bring back everyone starting from monitors, mds, osd. clients. > > Other while the osds missing will lead to a reconstruction of your cluster > that will not end with the return of the "faulty" osd(s). In the case you > turn off everything related to ceph cluster then it will be transparent for > the monitors and will not have to deal with partial reconstruction to clean > up and rescrubing of the returned OSD(s). > > best regards. > > Alphe Salas > T.I ingeneer. > > > > On 06/13/2014 04:56 AM, David wrote: >> >> Hi, >> >> We’re going to take down one OSD node for maintenance (add cpu + ram) >> which might take 10-20 minutes. >> What’s the best practice here in a production cluster running dumpling >> 0.67.7-1~bpo70+1? >> >> Kind Regards, >> David Majchrzak >> >> _______________________________________________ >> ceph-users mailing list >> ceph-users@lists.ceph.com >> http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com > > > _______________________________________________ > ceph-users mailing list > ceph-users@lists.ceph.com > http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com _______________________________________________ ceph-users mailing list ceph-users@lists.ceph.com http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
