Cloudera CDH/CDP 및 Hadoop EcoSystem, Semantic IoT등의 개발/운영 기술을 정리합니다. gooper@gooper.com로 문의 주세요.

hbase org.apache.hadoop.hbase.ClockOutOfSyncException: org.apache.hadoop.hbase.ClockOutOfSyncException 오류시 조치사항

총관리자 2016.07.14 20:37 조회 수 : 165

http://gsda1:16010/master-status를 확인하여 Region Servers부분에 원하는 서버가 포함되지 않으면

로그를 확인해서 아래와 같은 오류가 발생하면서 regionserver의 데몬이 기동하지 않는 경우는

각 서버에서 "rdate -s time.bora.net"를 실행하여 서버의 시간을 동기화 하고 "start-hbase.sh"을 실행하여 재 기동해준다.

(혹은 ntpdate time.bora.net를 실행한다)

------------------------------------오류사항---------------------------

FATAL [regionserver/gsda3/XXX.XXX.XXX.XXX:16020] regionserver.HRegionServer: Master rejected startup because clock is out of sync

org.apache.hadoop.hbase.ClockOutOfSyncException: org.apache.hadoop.hbase.ClockOutOfSyncException: Server gsda3,16020,1462235889101 has been rejected; Reported time is too far out of sync with master

. Time difference of 67249ms > max allowed of 30000ms

at org.apache.hadoop.hbase.master.ServerManager.checkClockSkew(ServerManager.java:388)

at org.apache.hadoop.hbase.master.ServerManager.regionServerStartup(ServerManager.java:262)

at org.apache.hadoop.hbase.master.MasterRpcServices.regionServerStartup(MasterRpcServices.java:322)

at org.apache.hadoop.hbase.protobuf.generated.RegionServerStatusProtos$RegionServerStatusService$2.callBlockingMethod(RegionServerStatusProtos.java:8615)

at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2117)

at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:104)

at org.apache.hadoop.hbase.ipc.RpcExecutor.consumerLoop(RpcExecutor.java:133)

at org.apache.hadoop.hbase.ipc.RpcExecutor$1.run(RpcExecutor.java:108)

at java.lang.Thread.run(Thread.java:745)

at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)

at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)

at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)

at java.lang.reflect.Constructor.newInstance(Constructor.java:422)

at org.apache.hadoop.ipc.RemoteException.instantiateException(RemoteException.java:106)

at org.apache.hadoop.ipc.RemoteException.unwrapRemoteException(RemoteException.java:95)

at org.apache.hadoop.hbase.protobuf.ProtobufUtil.getRemoteException(ProtobufUtil.java:325)

at org.apache.hadoop.hbase.regionserver.HRegionServer.reportForDuty(HRegionServer.java:2271)

at org.apache.hadoop.hbase.regionserver.HRegionServer.run(HRegionServer.java:893)

at java.lang.Thread.run(Thread.java:745)

Caused by: org.apache.hadoop.hbase.ipc.RemoteWithExtrasException(org.apache.hadoop.hbase.ClockOutOfSyncException): org.apache.hadoop.hbase.ClockOutOfSyncException: Server gsda3,16020,1462235889101 h

as been rejected; Reported time is too far out of sync with master. Time difference of 67249ms > max allowed of 30000ms