[ https://issues.apache.org/jira/browse/HBASE-3846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13030218#comment-13030218 ]
Hudson commented on HBASE-3846: ------------------------------- Integrated in HBase-TRUNK #1909 (See [https://builds.apache.org/hudson/job/HBase-TRUNK/1909/]) > 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