hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-14407) NotServingRegion: hbase region closed forever
Date Sun, 20 Sep 2015 19:53:04 GMT

    [ https://issues.apache.org/jira/browse/HBASE-14407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14900046#comment-14900046

Hadoop QA commented on HBASE-14407:

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  against 0.98 branch at commit a7afc132e2db7ebbb571b43ae17161bff40b59c5.
  ATTACHMENT ID: 12761343

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {color:green}+1 hadoop versions{color}. The patch compiles with all supported hadoop versions
(2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.0 2.7.0 2.7.1)

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of
javac compiler warnings.

    {color:green}+1 protoc{color}.  The applied patch does not increase the total number of
protoc compiler warnings.

    {color:red}-1 javadoc{color}.  The javadoc tool appears to have generated 22 warning messages.

    {color:green}+1 checkstyle{color}.  The applied patch does not increase the total number
of checkstyle errors

    {color:green}+1 findbugs{color}.  The patch does not introduce any  new Findbugs (version
2.0.3) warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number
of release audit warnings.

    {color:green}+1 lineLengths{color}.  The patch does not introduce lines longer than 100

  {color:green}+1 site{color}.  The mvn post-site goal succeeds with this patch.

    {color:green}+1 core tests{color}.  The patch passed unit tests in .

Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/15644//testReport/
Release Findbugs (version 2.0.3) 	warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/15644//artifact/patchprocess/newFindbugsWarnings.html
Checkstyle Errors: https://builds.apache.org/job/PreCommit-HBASE-Build/15644//artifact/patchprocess/checkstyle-aggregate.html

  Javadoc warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/15644//artifact/patchprocess/patchJavadocWarnings.txt
Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/15644//console

This message is automatically generated.

> NotServingRegion: hbase region closed forever
> ---------------------------------------------
>                 Key: HBASE-14407
>                 URL: https://issues.apache.org/jira/browse/HBASE-14407
>             Project: HBase
>          Issue Type: Bug
>          Components: Region Assignment
>    Affects Versions: 0.98.10, 1.2.0, 1.1.2, 1.3.0
>            Reporter: Shuaifeng Zhou
>            Assignee: Shuaifeng Zhou
>            Priority: Critical
>         Attachments: 14407-0.98.patch, 14407-branch-1.2.patch, hbase-14407-0.98.patch,
hbase-14407-1.1.patch, hbase-14407-1.2.patch, hs4.log, master.log
>     I found a situation may cause region closed forever, and this situation happend usually
on my cluster, version is 0.98.10, but 1.1.2 also have the problem:
>     1, master send region open to regionserver
>     2, rs open a handler do openregion
>     3, rs return resopnse to master
>     3, master not received the response, or timeout, send open region again
>     4, rs already opened the region
>     5, master processAlreadyOpenedRegion, update regionstate open in master memory
>     6, master received zk message region opened(for some reason late, eg: net work),
and triger update regionstate open, but find that region already opened, ERROR!
>     7, master send close region, and region be closed forever.

This message was sent by Atlassian JIRA

View raw message