[
https://issues.apache.org/jira/browse/HBASE-9441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13759982#comment-13759982
]
Hadoop QA commented on HBASE-9441:
----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12601765/9441-v5.txt
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 3 new
or modified tests.
{color:green}+1 hadoop1.0{color}. The patch compiles against the hadoop
1.0 profile.
{color:green}+1 hadoop2.0{color}. The patch compiles against the hadoop
2.0 profile.
{color:red}-1 javadoc{color}. The javadoc tool appears to have generated 1
warning messages.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) 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:red}-1 site{color}. The patch appears to cause mvn site goal to
fail.
{color:red}-1 core tests{color}. The patch failed these unit tests:
org.apache.hadoop.hbase.master.TestDistributedLogSplitting
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/7066//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7066//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7066//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7066//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7066//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7066//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7066//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7066//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7066//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/7066//console
This message is automatically generated.
> Intermittent TestRegionPlacement#testRegionPlacement failure
> ------------------------------------------------------------
>
> Key: HBASE-9441
> URL: https://issues.apache.org/jira/browse/HBASE-9441
> Project: HBase
> Issue Type: Test
> Reporter: Ted Yu
> Assignee: Ted Yu
> Priority: Minor
> Attachments: 9441-v1.txt, 9441-v2.txt, 9441-v3.txt, 9441-v4.txt,
> 9441-v5.txt, org.apache.hadoop.hbase.master.TestRegionPlacement-output.txt
>
>
> Occasionally TestRegionPlacement#testRegionPlacement fails due to no region
> found on secondary / tertiary region server.
> In the following test output, 10359edcfb1a761f94ab6d5b559c2278 was the region
> from the killed region server:
> {code}
> 2013-09-04 23:28:25,127 INFO [pool-1-thread-1] util.FSUtils(1878): Scan DFS
> for locality info takes 38 ms
> Region Assignment Verification for Table: testRegionAssignment
> Total regions : 10
> Total regions on favored nodes 10
> Total regions on PRIMARY region servers: 10
> Total regions on SECONDARY region servers: 0
> Total regions on TERTIARY region servers: 0
> ...
> 2013-09-04 23:28:25,130 DEBUG [pool-1-thread-1-EventThread]
> zookeeper.ZooKeeperWatcher(312): master:37502-0x140eb4dc4ef0000 Received
> ZooKeeper Event, type=NodeDataChanged, state=SyncConnected,
> path=/hbase/region-in-transition/10359edcfb1a761f94ab6d5b559c2278
> 2013-09-04 23:28:25,130 DEBUG [RS_OPEN_REGION-kiyo:49841-1]
> zookeeper.ZKAssign(861): regionserver:49841-0x140eb4dc4ef0007 Transitioned
> node 10359edcfb1a761f94ab6d5b559c2278 from RS_ZK_REGION_OPENING to
> RS_ZK_REGION_OPENED
> 2013-09-04 23:28:25,131 DEBUG [RS_OPEN_REGION-kiyo:49841-1]
> handler.OpenRegionHandler(386): Transitioned 10359edcfb1a761f94ab6d5b559c2278
> to OPENED in zk on kiyo.gq1.ygridcore.net,49841,1378337278470
> 2013-09-04 23:28:25,131 DEBUG [RS_OPEN_REGION-kiyo:49841-1]
> handler.OpenRegionHandler(187): Opened
> hbase:namespace,,1378337284888.10359edcfb1a761f94ab6d5b559c2278. on
> kiyo.gq1.ygridcore.net,49841,1378337278470
> 2013-09-04 23:28:25,132 DEBUG [AM.ZK.Worker-pool2-t6]
> master.AssignmentManager(801): Handling transition=RS_ZK_REGION_OPENED,
> server=kiyo.gq1.ygridcore.net,49841,1378337278470,
> region=10359edcfb1a761f94ab6d5b559c2278, current state from region state map
> ={10359edcfb1a761f94ab6d5b559c2278 state=OPENING, ts=1378337305025,
> server=kiyo.gq1.ygridcore.net,49841,1378337278470}
> 2013-09-04 23:28:25,132 INFO [AM.ZK.Worker-pool2-t6]
> master.RegionStates(263): Transitioned from {10359edcfb1a761f94ab6d5b559c2278
> state=OPENING, ts=1378337305025,
> server=kiyo.gq1.ygridcore.net,49841,1378337278470} to
> {10359edcfb1a761f94ab6d5b559c2278 state=OPEN, ts=1378337305132,
> server=kiyo.gq1.ygridcore.net,49841,1378337278470}
> 2013-09-04 23:28:25,132 DEBUG [AM.ZK.Worker-pool2-t6]
> handler.OpenedRegionHandler(150): Handling OPENED event for
> 10359edcfb1a761f94ab6d5b559c2278 from
> kiyo.gq1.ygridcore.net,49841,1378337278470; deleting unassigned node
> 2013-09-04 23:28:25,132 DEBUG [AM.ZK.Worker-pool2-t6]
> zookeeper.ZKAssign(405): master:37502-0x140eb4dc4ef0000 Deleting existing
> unassigned node 10359edcfb1a761f94ab6d5b559c2278 in expected state
> RS_ZK_REGION_OPENED
> 2013-09-04 23:28:25,188 INFO [pool-1-thread-1] hbase.ResourceChecker(171):
> after: master.TestRegionPlacement#testRegionPlacement Thread=873 (was 814)
> Potentially hanging thread: RS_OPEN_REGION-kiyo:53373-2
> ...
> - Thread LEAK? -, OpenFileDescriptor=1061 (was 1033) - OpenFileDescriptor
> LEAK? -, MaxFileDescriptor=32768 (was 32768), SystemLoadAverage=549 (was
> 609), ProcessCount=489 (was 489), AvailableMemoryMB=9288 (was 9107) -
> AvailableMemoryMB LEAK? -, ConnectionCount=23 (was 22) - ConnectionCount
> LEAK? -
> 2013-09-04 23:28:25,189 WARN [pool-1-thread-1] hbase.ResourceChecker(134):
> Thread=873 is superior to 500
> 2013-09-04 23:28:25,190 WARN [pool-1-thread-1] hbase.ResourceChecker(134):
> OpenFileDescriptor=1061 is superior to 1024
> 2013-09-04 23:28:25,223 DEBUG [pool-1-thread-1-EventThread]
> zookeeper.ZooKeeperWatcher(312): master:37502-0x140eb4dc4ef0000 Received
> ZooKeeper Event, type=NodeDeleted, state=SyncConnected,
> path=/hbase/region-in-transition/10359edcfb1a761f94ab6d5b559c2278
> 2013-09-04 23:28:25,224 DEBUG [pool-1-thread-1-EventThread]
> zookeeper.ZooKeeperWatcher(312): master:37502-0x140eb4dc4ef0000 Received
> ZooKeeper Event, type=NodeChildrenChanged, state=SyncConnected,
> path=/hbase/region-in-transition
> 2013-09-04 23:28:25,224 DEBUG [AM.ZK.Worker-pool2-t6]
> zookeeper.ZKAssign(434): master:37502-0x140eb4dc4ef0000 Deleted unassigned
> node 10359edcfb1a761f94ab6d5b559c2278 in expected state RS_ZK_REGION_OPENED
> 2013-09-04 23:28:25,225 DEBUG [AM.ZK.Worker-pool2-t6]
> master.AssignmentManager$4(1276): Znode
> hbase:namespace,,1378337284888.10359edcfb1a761f94ab6d5b559c2278. deleted,
> state: {10359edcfb1a761f94ab6d5b559c2278 state=OPEN, ts=1378337305132,
> server=kiyo.gq1.ygridcore.net,49841,1378337278470}
> 2013-09-04 23:28:25,225 INFO [AM.ZK.Worker-pool2-t6]
> master.RegionStates(299): Onlined 10359edcfb1a761f94ab6d5b559c2278 on
> kiyo.gq1.ygridcore.net,49841,1378337278470
> {code}
> Looks like region placement report was obtained when the region was still in
> transition.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
