The general idea is to use time for availability but not correctness. So a leader could be suspected as failed which may make the system unavailable until a new one is elected but consistency is not affected.
Alex On Fri, Jul 21, 2017 at 1:56 PM Michael Han <[email protected]> wrote: > One clarification on "System Time" here - ZK uses two type of time/clock > > * The wall-clock time, which is recorded as part of zNode stats such as > mtime and is exposed to users. > * The monotonic clock which ZK uses in various uses (e.g. failure > detection) to measure intervals. Note in 3.4 ZK still uses wall-clock for > interval measuring so you may see interesting behavior when your system > time change, but this will be fixed in the coming 3.4.11 release. > > On Fri, Jul 21, 2017 at 11:48 AM, Sandeep Singh <[email protected]> > wrote: > > > Adding the Amr question. > > Few things which I want to add is: > > > > Does zookeeper uses System Time for below things > > 1) Leader election > > 2) Deciding a slave is available/alive or not. > > 3) Deciding leader/master is alive or not. > > 4) Deciding a transaction timeout etc. > > 5) Ordering the transaction etc. > > > > regards, > > Sandeep. > > > > > > > > -- > > View this message in context: http://zookeeper-user.578899. > > n2.nabble.com/ZooKeeper-Time-Synchronization-tp7583217p7583223.html > > Sent from the zookeeper-user mailing list archive at Nabble.com. > > > > > > -- > Cheers > Michael. >
