You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Andrew Purtell (JIRA)" <ji...@apache.org> on 2011/05/03 01:26:03 UTC

[jira] [Commented] (HBASE-3846) Set RIT timeout higher

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

Andrew Purtell commented on HBASE-3846:
---------------------------------------

+1

> Set RIT timeout higher
> ----------------------
>
>                 Key: HBASE-3846
>                 URL: https://issues.apache.org/jira/browse/HBASE-3846
>             Project: HBase
>          Issue Type: Task
>    Affects Versions: 0.90.2
>            Reporter: Jean-Daniel Cryans
>            Assignee: Jean-Daniel Cryans
>            Priority: Critical
>             Fix For: 0.90.3
>
>         Attachments: HBASE-3846.patch
>
>
> As I was talking in HBASE-3669, it is really easy with the current RIT timeout to end up in situations where regions are doubly assigned, not assigned at all or assigned but the master doesn't know about it. As a bandaid, we should set hbase.master.assignment.timeoutmonitor.timeout to what the ZK session timeout is.
> We had to do that to one of our clusters to be able to start it, else the master kept racing with itself.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira