I am going to agree with Michael on this one. Don't change the clock skew, fix it.
On Fri, Mar 15, 2013 at 9:56 PM, Michel Segel <[email protected]> wrote: > Create an ntp server local to the cluster? This will eliminate the skew in > the first place. > > Sent from a remote device. Please excuse any typos... > > Mike Segel > > On Mar 15, 2013, at 3:53 PM, Ted Yu <[email protected]> wrote: > >> Are you using 0.94.x ? >> >> If so, see the following: >> >> maxSkew = c.getLong("hbase.master.maxclockskew", 30000); >> warningSkew = c.getLong("hbase.master.warningclockskew", 10000); >> ./src/main/java/org/apache/hadoop/hbase/master/ServerManager.java >> >> Cheers >> >> On Fri, Mar 15, 2013 at 3:49 PM, <[email protected]> wrote: >> >>> Hi, >>> >>> We recently encountered the issue that HBase tables got into a state that >>> was not disabled nor enabled. We found that the root cause was the linux >>> clock skewed more than 5 hours. I googled and understood that hbase can >>> only handle about a couple of seconds time skew. We were wondering if >>> there's any configuration in HBase that we can do so as to increase the >>> number of seconds that hbase could handle? >>> >>> Thanks very much, >>> >>> YuLing >>> -- Kevin O'Dell Customer Operations Engineer, Cloudera
