hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-1813) [hbase] OOME makes zombie of region server
Date Thu, 30 Aug 2007 22:18:31 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-1813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

stack updated HADOOP-1813:
--------------------------

    Attachment: failed_compaction.log

Another OOME in similar circumstance.  We go to compact a store that has 3 zero-length files
in it (Its holding references to another region).  We fail to create the compound file over
in compaction.dir because its 'already being created'.  Thereafter there is a flurry of regionserver
rolling out edits but no other activity.. then an OOME.  

Trying to look at the heap, the memory pressure has passed; no obvious retention going on
looking at a dump w/ jhat.

> [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
>            Priority: Minor
>         Attachments: failed_compaction.log
>
>
> 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.


Mime
View raw message