hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Prakash Khemani (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-4007) distributed log splitting can get indefinitely stuck
Date Thu, 25 Aug 2011 21:40:33 GMT

    [ https://issues.apache.org/jira/browse/HBASE-4007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13091345#comment-13091345
] 

Prakash Khemani commented on HBASE-4007:
----------------------------------------

(I had tried using reviewboard yesterday but it was fataling on me - Internal Server Error
500. Thanks for reviewing the patch the hard way)
==

For deadWorkers - one of the goals was to not block handleDeadWorkers() and worry about deadlocks
etc. I could have used ConcurrentSet but I was not sure of the semantics - how an iterator
behaves when another item is added.

I will change this to use ConcurrentSet ... please let me know.


==

I will change registerHeartbeat() to hearbeat().



> 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
>         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

        

Mime
View raw message