On Tue, 26 Feb 2013, Stefan Priebe - Profihost AG wrote: > But that redults in a 1-3s hickup for all KVM vms. This is not what I want. You can do kill $pid ceph osd down $osdid (or even reverse the order, if the sequence is quick enough) to avoid waiting for the failure detection delay. But if the OSDs are going down, then the peering has to happen one way or another. sage > > Stefan > > Am 26.02.2013 um 18:06 schrieb Sage Weil <sage@xxxxxxxxxxx>: > > > On Tue, 26 Feb 2013, Stefan Priebe - Profihost AG wrote: > >> Hi list, > >> > >> how can i do a short maintanance like a kernel upgrade on an osd host? > >> Right now ceph starts to backfill immediatly if i say: > >> ceph osd out 41 > >> ... > >> > >> Without ceph osd out command all clients hang for the time ceph does not > >> know that the host was rebootet. > >> > >> I tried > >> ceph osd set nodown and ceph osd set noout > >> but this doesn't result in any difference > > > > For a temporary event like this, you want the osd to be down (so that io > > can continue with remaining replicas) but NOT to mark it out (so that data > > doesn't get rebalanced). The simplest way to do that is > > > > ceph osd set noout > > killall ceph-osd > > .. reboot .. > > > > Just remember to do > > > > ceph osd unset noout > > > > when you are done so that future osds that fail will get marked out on > > their own after the 5 minute (default) interval. > > > > sage > > > > -- > > To unsubscribe from this list: send the line "unsubscribe ceph-devel" in > > the body of a message to majordomo@xxxxxxxxxxxxxxx > > More majordomo info at http://vger.kernel.org/majordomo-info.html > > -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
