It worked. J thanks.
From: [email protected] [mailto:[email protected]] On Behalf Of Eric Newton Sent: Friday, July 26, 2013 11:46 AM To: [email protected] Subject: Re: Changing Time on Server Yes, I think that will work. On Fri, Jul 26, 2013 at 10:36 AM, Ott, Charles H. <[email protected]> wrote: Do you think this bash script would be okay to run on a server with zookeeper? It is designed to increment the system clock by 1 second every 10 seconds for 960 loops (16 minutes) #! /usr/bin/env bash #Increase server time by 960 seconds(16mins) over a 9600 second(2hrs40mins) period. for i in {1..960} do later=$(date --date="+1 second") date -s "$later" sleep 10 done Thanks, Charles From: [email protected] [mailto:[email protected]] On Behalf Of Eric Newton Sent: Friday, July 26, 2013 8:43 AM To: [email protected] Subject: Re: Changing Time on Server Yes, yanking the time around by more than the zookeeper timeout can cause havoc, since the system cannot reason about session guarantees. But moving the time around by a few seconds should be fine. The changes for ACCUMULO-1572 might help. -Eric On Thu, Jul 25, 2013 at 11:03 PM, Ott, Charles H. <[email protected]> wrote: I know this question may be a bit off topic for Accumulo, but I am curious about Zookeeper and changing server time. Is it possible to correct the clock on a server without zookeeper/hadoop/accumulo combination breaking on a development VM with all three services running? Last time I tried to do it, I believe zookeeper wasnt able to track sessions properly, and everything failed to communicate.
