[
https://issues.apache.org/jira/browse/HBASE-4816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13152544#comment-13152544
]
Hadoop QA commented on HBASE-4816:
----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12504151/4816.txt
against trunk revision .
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified
tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
-1 patch. The patch command could not apply the patch.
Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/286//console
This message is automatically generated.
> 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
> Fix For: 0.92.0
>
> Attachments: 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
