[
https://issues.apache.org/jira/browse/HBASE-4007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13100085#comment-13100085
]
Prakash Khemani commented on HBASE-4007:
----------------------------------------
Hi Stack, I have not pushed this out to production yet ... and the way things
are it will be a while before we do the next push to the hbase-90 tiers.
I will try to get some cluster testing done and will update this thread.
Regarding the use of ConcurrentHashMap as opposed to HashSet + ObjectLock : I
could not find any nice way to take a snapshot of a concurrent-hash-map. The
way the code is written I need to take a snapshot of the deadWorkers set.
I have just rebased. I will try to put it up in the reviewboard one more time.
Thanks,
Prakash
> distributed log splitting can get indefinitely stuck
> ----------------------------------------------------
>
> Key: HBASE-4007
> URL: https://issues.apache.org/jira/browse/HBASE-4007
> Project: HBase
> Issue Type: Bug
> Reporter: Prakash Khemani
> Assignee: Prakash Khemani
> Priority: Critical
> Fix For: 0.92.0
>
> Attachments:
> 0001-HBASE-4007-distributed-log-splitting-can-get-indefin.patch
>
>
> After the configured number of retries SplitLogManager is not going to
> resubmit log-split tasks. In this situation even if the splitLogWorker that
> owns the task dies the task will not get resubmitted.
> When a regionserver goes away then all the split-log tasks that it owned
> should be resubmitted by the SplitLogMaster.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
