Hi Sage, On 04/03/2013 09:58 AM, Sage Weil wrote: > Hi Jim, > > What happens if you change 'osd mon ack timeout = 300' (from the > default of 30)? I suspect part of the problem is that the mons are just > slow enough that the osd's resend the same thing again and it snowballs > into more work for the monitor. Thanks, that helped. My OSDs aren't reconnecting to the mon any more, and the new filesystem started up as expected. Hmmm, it occurs to me that I upgraded my mon hosts to 10 GbE NICs at about the same time I started testing v0.59. Perhaps before the upgrade I was running right at the edge of that timeout. After the NIC upgrade the PGStat messages come flooding in at startup, and they bunch up enough that working through the backlog pushed me over the timeout cliff? Is there any downside to using a large 'osd mon ack timeout', assuming I run more than one mon? If so, I expect I'll work my way back from 'osd mon ack timeout = 300' to see how big it needs to be to stay reliable for my configuration. Sorry for the noise about paxos. At least it was useful to help Joao find that debug log message that was more expensive than expected.... Thanks -- Jim > > 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
