On Mar 12, 2014, at 10:44 AM, Gandalf Corvotempesta <gandalf.corvotempesta@xxxxxxxxx> wrote: > 2014-01-30 18:41 GMT+01:00 Eric Eastman <eric0e@xxxxxxx>: >> I have this problem on some of my Ceph clusters, and I think it is due to >> the older hardware the I am using does not have the best clocks. To fix the >> problem, I setup one server in my lab to be my local NTP time server, and >> then on each of my Ceph monitors, in the /etc/ntp.conf file, I put in a >> single "server" line that reads: >> >> server XX.XX.XX.XX iburst burst minpoll 4 maxpoll 5 > > I'm using a local NTP server, all Mons are synced with local NTP but > ceph still detect a clock skew Machine clocks aren't perfect, even with NTP. Ceph by default is very sensitive. I usually add this to my ceph.conf to prevent the warnings: [mon] mon clock drift allowed = .500 That is, allow the clocks to drift up to 1/2 second before saying anything. JN _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
 |