[
https://issues.apache.org/jira/browse/HBASE-6018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13277686#comment-13277686
]
Anoop Sam John commented on HBASE-6018:
---------------------------------------
I feel this change should be fine enough to handle our requirement.
We make the core threads count = max threads count and use an unbounded queue.
"hbasefsck.numthreads" -> By this count we mean ideally that these many
parallel operations can run.
As we make the core threads count as this value rather than 1, the submitted
tasks will create new threads or allocat to available threads. Only when more
than these many requests, those will get queued.
Also we make executor.allowCoreThreadTimeOut(true). So there is absolutely no
problem in increasing the core threads count from 1..
> hbck fails with a RejectedExecutionException
> --------------------------------------------
>
> Key: HBASE-6018
> URL: https://issues.apache.org/jira/browse/HBASE-6018
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.92.1, 0.94.0
> Reporter: Jonathan Hsieh
> Assignee: Jonathan Hsieh
> Attachments: hbase-6018-v2.patch, hbase-6018.patch
>
>
> On a long running job 0.94.0rc3 cluster, we get to a point where hbck
> consistently encounters this error and fails:
> {code}
> Exception in thread "main" java.util.concurrent.RejectedExecutionException
> at
> java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:1768)
> at
> java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:767)
> at
> java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:658)
> at
> org.apache.hadoop.hbase.util.HBaseFsck.loadHdfsRegionInfos(HBaseFsck.java:633)
> at
> org.apache.hadoop.hbase.util.HBaseFsck.onlineConsistencyRepair(HBaseFsck.java:354)
> at org.apache.hadoop.hbase.util.HBaseFsck.onlineHbck(HBaseFsck.java:382)
> at org.apache.hadoop.hbase.util.HBaseFsck.main(HBaseFsck.java:3120)
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
