I'm not aware of there being an issue, we typically only use the clock for relative time around session expiration. If the clock does skew a significant amount we can run into issues like the following, but a single second seems unlikely to cause issues: https://issues.apache.org/jira/browse/ZOOKEEPER-1366
See this analysis from 2012 when, iirc, ZK did run into issues in a small number of cases. Note however that this was due to jvm/os interaction issues and not ZooKeeper itself: http://blog.cloudera.com/blog/2012/07/watching-the-clock-clouderas-response-to-leap-second-troubles/ Patrick On Thu, Jun 11, 2015 at 7:55 AM, Camille Fournier <[email protected]> wrote: > I'm honestly not sure. This blog post from datastax on the JVM > vulnerabilities to the leap second bug might be educational. > http://www.datastax.com/dev/blog/preparing-for-the-leap-second > Anyone else have any ideas? > > Thanks, > C > > On Wed, Jun 10, 2015 at 5:12 PM, jawhny cooke <[email protected]> wrote: > >> Is ZK vulnerable to the 6/30/15 leap second event? If so, what preventative >> steps are required to mitigate impact? >> >> My apologies if this has already been asked and answered. >> >> -- >> Warm Regards, >> >> -JC >>
