I am using 1.2.5 (revision=d7b05f79dee10e0ada614765bb354b93d615a157)

Yes, I see NPE repeatedly.
This occurs every minute.

Should I fix it?

Best regards,
Minwoo Kang

________________________________________
보낸 사람: Kang Minwoo <minwoo.k...@outlook.com>
보낸 날짜: 2017년 7월 6일 목요일 오전 9:29:35
받는 사람: user@hbase.apache.org
제목: NPE in ReplicationZKLockCleanerChore

Hello, HBase Users.

While I am watching HMaster log, I found NullPointerException Logs.

--------

2017-07-06 09:05:02,579 DEBUG [,1498445640728_ChoreService_1] 
cleaner.CleanerChore: Removing: hdfs://*** from archive
2017-07-06 09:05:02,585 ERROR [,1498445640728_ChoreService_2] 
hbase.ScheduledChore: Caught error
java.lang.NullPointerException
        at 
org.apache.hadoop.hbase.master.cleaner.ReplicationZKLockCleanerChore.chore(ReplicationZKLockCleanerChore.java:80)
        at org.apache.hadoop.hbase.ScheduledChore.run(ScheduledChore.java:185)
        at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
        at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304)
        at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)
        at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
        at 
org.apache.hadoop.hbase.JitterScheduledThreadPoolExecutorImpl$JitteredRunnableScheduledFuture.run(JitterScheduledThreadPoolExecutorImpl.java:110)
        at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
        at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
        at java.lang.Thread.run(Thread.java:745)
2017-07-06 09:05:02,585 DEBUG [,1498445640728_ChoreService_1] 
cleaner.CleanerChore: Removing: hdfs://*** from archive
2017-07-06 09:05:02,586 DEBUG [,1498445640728_ChoreService_1] 
cleaner.CleanerChore: Removing: hdfs://*** from archive

--------

I wonder what side effects this error gives HBase.

Best regards,
Minwoo Kang

Reply via email to