Ceph Clock offset fault handling

Clock offset Symptom:

[Email protected] ~]# ceph-w

Cluster b516386f-cb9d-49d5-bf48-07f0dac29e97

Health Health_warn 192 pgs degraded; 192 pgs stuck Unclean

Monmap E1:3 mons at {node1=10.240.217.101:6789/0,node4=10.240.217.104:6789/0,node5=10.240.217.105:6789/0}, election Epoch, quorum 0,1,2 NODE1,NODE4,NODE5

Osdmap E63:3 osds:2 up, 2 in

Pgmap v249:192 pgs, 3 pools, 0 bytes data, 0 objects

10314 MB used, 2063 gb/2073 GB Avail

192 active+degraded

2014-06-19 10:46:24.736860 mon.0 [WRN] mon.1 10.240.217.104:6789/0 clock skew 0.060021s > Max 0.05s

Ways to solve the above problem:

Ceph default clock offset time is 0.05s, because this time is too small, causing the time offset between the cluster value is greater than 0.05s, to solve this problem

You need to modify the configuration of ceph.conf to each monitor node by adding the following configuration to the configuration file

[Email protected] ~]# vi/etc/ceph/ceph.conf

[Mon]

Mon clock Drift allowed =. 50

Restart the Ceph process after modification

[[Email protected] ~]# service Ceph restart

= = = Mon.node1 = =

= = = Mon.node1 = =

Stopping Ceph mon.node1 on Node1...kill 4723...done

= = = Mon.node1 = =

Starting Ceph mon.node1 on Node1 ...

Starting Ceph-create-keys on Node1 ...

More detailed procedures can be seen in official documents

http://ceph.com/docs/master/rados/configuration/mon-config-ref/#monitor-store-synchronization

This article is from the "Zhangdh Open Space" blog, so be sure to keep this source http://linuxblind.blog.51cto.com/7616603/1710173

Ceph Clock offset fault handling