[
https://issues.apache.org/jira/browse/HBASE-2656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-2656:
-------------------------
Priority: Blocker (was: Major)
Making this unexplained behavior a blocker.
I just disabled this test, in essence, removing the assertion that the pair
returned is not null because this opposite assertion is not always true up on
hudson -- see
http://hudson.zones.apache.org/hudson/view/HBase/job/HBase-TRUNK/1336/ for
example.
> 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
> Priority: Blocker
>
> 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.
