You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Karthik Ranganathan (JIRA)" <ji...@apache.org> on 2010/06/12 01:11:13 UTC
[jira] Commented: (HBASE-2656) HMaster.getRegionTableClosest should
not return null for closed regions
[ https://issues.apache.org/jira/browse/HBASE-2656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12878128#action_12878128 ]
Karthik Ranganathan commented on HBASE-2656:
--------------------------------------------
TestMaster was the test to tracki this behavior, which seems to have changed since HBASE-2656.
This is a comment to verify what has changed in TestMaster and fix the test so that the correct functionality is verified. There is a TODO in the code now:
/**
* TODO: The assertNull below used to work before moving all RS->M
* communication to ZK, find out why this test's behavior has changed.
* Tracked in HBASE-2656.
assertNull(pair);
*/
> HMaster.getRegionTableClosest should not return null for closed regions
> -----------------------------------------------------------------------
>
> Key: HBASE-2656
> URL: https://issues.apache.org/jira/browse/HBASE-2656
> Project: HBase
> Issue Type: Bug
> Components: master
> Affects Versions: 0.21.0
> Reporter: Todd Lipcon
>
> Raised in the review of HBASE-2560: there are a couple functions in HMaster which return null when a region has not been deployed. Instead, they should return a Pair<HRegionInfo, HServerAddress> where only the address is null (since the info is still in meta!)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.