[
https://issues.apache.org/jira/browse/HBASE-4153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13106777#comment-13106777
]
stack commented on HBASE-4153:
------------------------------
There are some tabs in your patch. Be careful.
Rather than do this check for Open/Close, why not throw different exceptions
dependent on whether it open or close? Subclass
RegionAlreadyInTransitionException. Then you wouldn't have to do this fragile
String compare or do these defines of things like RECEIVED, OPEN (with a space)
and CLOSE (with a space).
The changes in TestOpenRegionHandler are good.
> Handle RegionAlreadyInTransitionException in AssignmentManager
> --------------------------------------------------------------
>
> Key: HBASE-4153
> URL: https://issues.apache.org/jira/browse/HBASE-4153
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.92.0
> Reporter: Jean-Daniel Cryans
> Assignee: ramkrishna.s.vasudevan
> Fix For: 0.92.0
>
> Attachments: 4153-v3.txt, HBASE-4153_1.patch, HBASE-4153_2.patch,
> HBASE-4153_3.patch
>
>
> Comment from Stack over in HBASE-3741:
> {quote}
> Question: Looking at this patch again, if we throw a
> RegionAlreadyInTransitionException, won't we just assign the region elsewhere
> though RegionAlreadyInTransitionException in at least one case here is saying
> that the region is already open on this regionserver?
> {quote}
> Indeed looking at the code it's going to be handled the same way other
> exceptions are. Need to add special cases for assign and unassign.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
