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 (JIRA)" <ji...@apache.org> on 2011/08/09 12:45:28 UTC

[jira] [Updated] (HBASE-4182) NullPointerException when loadbalancer tries to close the region for reassigning to new RS.

     [ https://issues.apache.org/jira/browse/HBASE-4182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ramkrishna.s.vasudevan updated HBASE-4182:
------------------------------------------

    Fix Version/s: 0.92.0

> NullPointerException when loadbalancer tries to close the region for reassigning to new RS.
> -------------------------------------------------------------------------------------------
>
>                 Key: HBASE-4182
>                 URL: https://issues.apache.org/jira/browse/HBASE-4182
>             Project: HBase
>          Issue Type: Bug
>            Reporter: ramkrishna.s.vasudevan
>            Assignee: ramkrishna.s.vasudevan
>             Fix For: 0.92.0
>
>
> 1. Start 2 RS.  Create some regions so that is is balanced.
> 2. Stop RS2.  Now all the Regions from RS2 are assigned to RS1.
> 3. Again start RS2.
> 4. Load Balancing is calculated and few regions from RS1 are assigned to RS2.
> As part of this step Master tries to unassign the regions from RS1.
> {noformat}
>           RegionTransitionData data = ZKAssign.getDataNoWatch(zkw, ZKAssign
>               .getNodeName(zkw, region.getEncodedName()), null);
>           if (data.equals(EventType.RS_ZK_REGION_CLOSING)) {
>             ZKAssign.createNodeClosing(zkw, region, master.getServerName());
>           }
> {noformat}
> Now there is no data present in the unassigned node.  We are directly comparing the data.
> Here data is null. Hence nullpointer exception is thrown.
> Hence load balancing fails.

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