Baiqiang Zhao created HBASE-23287:
-------------------------------------
Summary: LogCleaner is not added to choreService
Key: HBASE-23287
URL: https://issues.apache.org/jira/browse/HBASE-23287
Project: HBase
Issue Type: Bug
Components: wal
Affects Versions: 1.4.11, 1.6.0
Reporter: Baiqiang Zhao
We found /hbase/oldWALs keeps growing, and we never use replication feature.
Then we found OldWALsCleaner thread is always in WAITTING state :
{code:java}
Thread 176 (OldWALsCleaner-1): State: WAITING Blocked count: 0 Waited count: 1
Waiting on
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@2ef05d36
Stack: sun.misc.Unsafe.park(Native Method)
java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039)
java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442)
org.apache.hadoop.hbase.master.cleaner.LogCleaner.deleteFile(LogCleaner.java:185)
org.apache.hadoop.hbase.master.cleaner.LogCleaner.access$000(LogCleaner.java:48)
org.apache.hadoop.hbase.master.cleaner.LogCleaner$1.run(LogCleaner.java:161)
java.lang.Thread.run(Thread.java:745)
{code}
Finally, we found that LogCleaner is not added to choreService, so LogCleaner
doesn't run periodically.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)