hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-616) " We slept XXXXXX ms, ten times longer than scheduled: 3000" happens frequently.
Date Wed, 07 May 2008 19:50:55 GMT

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

stack commented on HBASE-616:
-----------------------------

Looking at a log which has a bunch of these in it -- the user has set timeout to 3minutes
instead of default one minute -- and they seem to happen when a compaction is running.  It
may be possible that compaction on weaker boxes can make it so other threads are starved.

> " We slept XXXXXX ms, ten times longer than scheduled: 3000" happens frequently.
> --------------------------------------------------------------------------------
>
>                 Key: HBASE-616
>                 URL: https://issues.apache.org/jira/browse/HBASE-616
>             Project: Hadoop HBase
>          Issue Type: Bug
>            Reporter: stack
>
> Just saw the below in a log... all in a row on the one server.
> {code}
>    4493 2008-05-05 18:08:17,512 WARN org.apache.hadoop.hbase.util.Sleeper: We slept 34557ms,
ten times longer than scheduled: 3000
>    4494 2008-05-05 18:11:08,879 WARN org.apache.hadoop.hbase.util.Sleeper: We slept 30576ms,
ten times longer than scheduled: 3000
>    4495 2008-05-05 18:30:45,056 WARN org.apache.hadoop.hbase.util.Sleeper: We slept 1091720ms,
ten times longer than scheduled: 3000
>    4496 2008-05-05 18:30:45,056 WARN org.apache.hadoop.hbase.util.Sleeper: We slept 1094209ms,
ten times longer than scheduled: 10000
>    4497 2008-05-05 18:30:45,429 FATAL org.apache.hadoop.hbase.HRegionServer: unable to
report to master for 1092093 milliseconds - aborting server
> {code}
> We're seeing these kinda outages pretty frequently.  In the case above, it was small
cluster that was using TableReduce to insert.  The MR, HDFS and HBase were all running on
same nodes.

-- 
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