[
https://issues.apache.org/jira/browse/HBASE-4816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13153253#comment-13153253
]
Hudson commented on HBASE-4816:
-------------------------------
Integrated in HBase-0.92 #144 (See
[https://builds.apache.org/job/HBase-0.92/144/])
HBASE-4816 Regionserver wouldn't go down because split happened exactly at
same time we issued bulk user region close call on our way out
stack :
Files :
* /hbase/branches/0.92/CHANGES.txt
*
/hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/regionserver/HRegionServer.java
*
/hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/regionserver/SplitRequest.java
> Regionserver wouldn't go down because split happened exactly at same time we
> issued bulk user region close call on our way out
> ------------------------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-4816
> URL: https://issues.apache.org/jira/browse/HBASE-4816
> Project: HBase
> Issue Type: Bug
> Reporter: stack
> Assignee: stack
> Fix For: 0.92.0
>
> Attachments: 4816-v2.txt, 4816.txt
>
>
> A regionserver wouldn't go down because it was waiting on a user region to
> close only the user-space region had just been opened as part of a split
> transaction -- it was a new daughter -- just as we'd issued the bulk close to
> all user regions on receipt of a cluster shutdown call.
> We need to add a check for this condition -- user tables that did not get the
> close.
--
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
