My advice is leverage Linux cgroup to isolate some resource for critical part of Ceph. Such as state of heartbeat, replication of OSDs. Even the timeout set to many minutes, there always are bigger heavy loading on Ceph. Wales Wang 在 2013-5-14，下午11:30，Sage Weil <sage@xxxxxxxxxxx> 写道： > On Tue, 14 May 2013, Chen, Xiaoxi wrote: >> >> Hi >> >> We are suffering our OSD flipping between up and down ( OSD X be voted to >> down due to 3 missing ping, and after a while it tells the monitor ?map xxx >> wrongly mark me down? ). Because we are running sequential write performance >> test on top of RBDs, and the cluster network nics is really in high >> utilization (8Gb/s+ for a 10Gb network). >> >> Is this a expected behavior ? or how can I prevent this happen? > > You an increase the heartbeat grace period. The pings are handled by a > separate thread on the backside interface (if there is one). If you are > missing pings then the network or scheduler is preventing those (small) > messages from being processed (there is almost no lock contention in that > path). Which means it really is taking ~20 seconds or wahtever to handle > those messages. It's really a questin of how unresponsive you want to > permit the OSDs to be before you consider it a failure.. > > sage > _______________________________________________ > ceph-users mailing list > ceph-users@xxxxxxxxxxxxxx > http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com -- 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
