You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "ramkrishna.s.vasudevan (Commented) (JIRA)" <ji...@apache.org> on 2012/01/20 19:11:40 UTC

[jira] [Commented] (HBASE-5237) Addendum for HBASE-5160 and HBASE-4397

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

ramkrishna.s.vasudevan commented on HBASE-5237:
-----------------------------------------------

Attached patch for 0.90 and trunk.
Please review.  Will fix in 0.90 and trunk.  Pls check if needed in 0.92 also.
                
> Addendum for HBASE-5160 and HBASE-4397
> --------------------------------------
>
>                 Key: HBASE-5237
>                 URL: https://issues.apache.org/jira/browse/HBASE-5237
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 0.90.5
>            Reporter: ramkrishna.s.vasudevan
>            Assignee: ramkrishna.s.vasudevan
>             Fix For: 0.92.0, 0.90.6
>
>         Attachments: HBASE-5237_0.90.patch, HBASE-5237_trunk.patch
>
>
> As part of HBASE-4397 there is one more scenario where the patch has to be applied.
> {code}
> RegionPlan plan = getRegionPlan(state, forceNewPlan);
>       if (plan == null) {
>         debugLog(state.getRegion(),
>             "Unable to determine a plan to assign " + state);
>         return; // Should get reassigned later when RIT times out.
>       }
> {code}
> I think in this scenario also 
> {code}
> this.timeoutMonitor.setAllRegionServersOffline(true);
> {code}
> this should be done.

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