On 05/14/2013 10:30 AM, Sage Weil wrote:
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
It might be worth testing out how long pings or other network traffic are taking during these tests. There may be some tcp tunning you can do here, or even consider using a separate network for the mons.
Mark -- 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
