[
https://issues.apache.org/jira/browse/HADOOP-1813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12527729
]
Hadoop QA commented on HADOOP-1813:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12365909/oome-3.patch
against trunk revision r575889.
@author +1. The patch does not contain any @author tags.
javadoc +1. The javadoc tool did not generate any warning messages.
javac +1. The applied patch does not generate any new compiler warnings.
findbugs +1. The patch does not introduce any new Findbugs warnings.
core tests -1. The patch failed core unit tests.
contrib tests +1. The patch passed contrib unit tests.
Test results:
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/769/testReport/
Findbugs warnings:
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/769/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/769/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/769/console
This message is automatically generated.
> [hbase] OOME makes zombie of region server
> ------------------------------------------
>
> Key: HADOOP-1813
> URL: https://issues.apache.org/jira/browse/HADOOP-1813
> Project: Hadoop
> Issue Type: Bug
> Components: contrib/hbase
> Reporter: stack
> Assignee: stack
> Fix For: 0.15.0
>
> Attachments: failed_compaction.log, oome-2.patch, oome-3.patch,
> oome.patch
>
>
> We need to catch Errors in the main regionserver and master run methods.
> During a cluster loading, an OOME made main thread exit but server stayed up
> doing a zombie-impersonation. For OOME's we could add an attempted handler.
> Service threads also need to be 'daemon'-ified. Here's an extract from
> thread dump of hung region server:
> {code}
> Full thread dump Java HotSpot(TM) Server VM (1.6.0_01-b06 mixed mode):
> ...
> "Lease.monitor" prio=10 tid=0x082ec800 nid=0x41ca waiting on condition
> [0xb122d000..0xb122df30]
> java.lang.Thread.State: TIMED_WAITING (sleeping)
> at java.lang.Thread.sleep(Native Method)
> at org.apache.hadoop.hbase.Leases$LeaseMonitor.run(Leases.java:226)
> at java.lang.Thread.run(Thread.java:619)
> "Thread-10.logRoller" prio=10 tid=0x082eb400 nid=0x41c9 waiting on condition
> [0xb127e000..0xb127eeb0]
> java.lang.Thread.State: TIMED_WAITING (sleeping)
> at java.lang.Thread.sleep(Native Method)
> at
> org.apache.hadoop.hbase.HRegionServer$LogRoller.run(HRegionServer.java:379)
> at java.lang.Thread.run(Thread.java:619)
> "Thread-10.cacheFlusher" prio=10 tid=0x082ea000 nid=0x41c7 waiting on
> condition [0xb1320000..0xb1320fb0]
> java.lang.Thread.State: TIMED_WAITING (sleeping)
> at java.lang.Thread.sleep(Native Method)
> at
> org.apache.hadoop.hbase.HRegionServer$Flusher.run(HRegionServer.java:325)
> at java.lang.Thread.run(Thread.java:619)
> "Thread-10.worker" prio=10 tid=0x082e9400 nid=0x41c6 waiting on condition
> [0xb1371000..0xb1372130]
> java.lang.Thread.State: TIMED_WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> - parking to wait for <0xb649a288> (a
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
> at
> java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:198)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:1927)
> at
> java.util.concurrent.LinkedBlockingQueue.poll(LinkedBlockingQueue.java:395)
> at
> org.apache.hadoop.hbase.HRegionServer$Worker.run(HRegionServer.java:859)
> at java.lang.Thread.run(Thread.java:619)
> ...
> {code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
