Return-Path: X-Original-To: apmail-zookeeper-user-archive@www.apache.org Delivered-To: apmail-zookeeper-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id BE0A01749D for ; Thu, 11 Jun 2015 22:44:39 +0000 (UTC) Received: (qmail 9381 invoked by uid 500); 11 Jun 2015 22:44:39 -0000 Delivered-To: apmail-zookeeper-user-archive@zookeeper.apache.org Received: (qmail 9325 invoked by uid 500); 11 Jun 2015 22:44:39 -0000 Mailing-List: contact user-help@zookeeper.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@zookeeper.apache.org Delivered-To: mailing list user@zookeeper.apache.org Received: (qmail 9314 invoked by uid 99); 11 Jun 2015 22:44:39 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 11 Jun 2015 22:44:39 +0000 Received: from mail-la0-f48.google.com (mail-la0-f48.google.com [209.85.215.48]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id 965631A0605 for ; Thu, 11 Jun 2015 22:44:38 +0000 (UTC) Received: by laew7 with SMTP id w7so11383828lae.1 for ; Thu, 11 Jun 2015 15:44:37 -0700 (PDT) X-Received: by 10.112.42.16 with SMTP id j16mr12026923lbl.98.1434062677164; Thu, 11 Jun 2015 15:44:37 -0700 (PDT) MIME-Version: 1.0 Received: by 10.25.87.75 with HTTP; Thu, 11 Jun 2015 15:43:56 -0700 (PDT) In-Reply-To: References: From: Patrick Hunt Date: Thu, 11 Jun 2015 15:43:56 -0700 Message-ID: Subject: Re: Q: Is ZK vulnerable Leap Second in 2015 To: UserZooKeeper Content-Type: text/plain; charset=UTF-8 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 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 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 >>