[
https://issues.apache.org/jira/browse/HBASE-5882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13279023#comment-13279023
]
Zhihong Yu commented on HBASE-5882:
-----------------------------------
{code}
+ } else if (wasOnDeadServer(sn, deadServers)){
{code}
since regionInfo was not one of the parameters to wasOnDeadServer(), the method
name still doesn't make sense.
I think we can directly place the check ( deadServers.keySet().contains(sn) )
above. This way there is no need to introduce a new method.
> Prcoess RIT on master restart can try assigning the region if the region is
> found on a dead server instead of waiting for Timeout Monitor
> -----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-5882
> URL: https://issues.apache.org/jira/browse/HBASE-5882
> Project: HBase
> Issue Type: Improvement
> Affects Versions: 0.90.6, 0.92.1
> Reporter: ramkrishna.s.vasudevan
> Assignee: ramkrishna.s.vasudevan
> Attachments: hbase_5882.patch, hbase_5882_V2.patch,
> hbase_5882_V3.patch
>
>
> Currently on master restart if it tries to do processRIT, any region if
> found on dead server tries to avoid the nwe assignment so that timeout
> monitor can take care.
> This case is more prominent if the node is found in RS_ZK_REGION_OPENING
> state. I think we can handle this by triggering a new assignment with a new
> plan.
--
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
