[
https://issues.apache.org/jira/browse/HBASE-508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-508:
------------------------
Attachment: td.log
Thread dump shows all threads present and not deadlocked.
Why would we not be scheduling flushes and compactions?
This server will probably keep going and then OOME.
> regionserver stuck log rolling and doing nothing else
> -----------------------------------------------------
>
> Key: HBASE-508
> URL: https://issues.apache.org/jira/browse/HBASE-508
> Project: Hadoop HBase
> Issue Type: Bug
> Reporter: stack
> Attachments: td.log
>
>
> When I look in the log of XX.XX.XX.92, it shows only log rolling activity of
> following form:
> {code}
> ...
> 2008-03-13 07:04:17,596 DEBUG org.apache.hadoop.hbase.HLog: Closing current
> log writer
> hdfs://coral-dfs.cluster.powerset.com:10000/hbase/XX.XX.XX-2.u.powerset.com/log_XX.XX.XX.92_1205384328364_60020/hlog.dat.022
> to get a new one
> 2008-03-13 07:04:17,599 INFO org.apache.hadoop.hbase.HLog: new log writer
> created at
> hdfs://coral-dfs.cluster.powerset.com:10000/hbase/XX.XX.XX-2.u.powerset.com/log_XX.XX.XX.92_1205384328364_60020/hlog.dat.023
> 2008-03-13 07:08:48,425 INFO org.apache.hadoop.hbase.HRegionServer: Rolling
> hlog. Number of entries: 30004
> 2008-03-13 07:08:48,472 DEBUG org.apache.hadoop.hbase.HLog: Closing current
> log writer
> hdfs://coral-dfs.cluster.powerset.com:10000/hbase/XX.XX.XX-2.u.powerset.com/log_XX.XX.XX.92_1205384328364_60020/hlog.dat.023
> to get a new one
> 2008-03-13 07:08:48,484 INFO org.apache.hadoop.hbase.HLog: new log writer
> created at
> hdfs://coral-dfs.cluster.powerset.com:10000/hbase/XX.XX.XX-2.u.powerset.com/log_XX.XX.XX.92_1205384328364_60020/hlog.dat.024
> ~
> ...
>
>
> {code}
> .. which is odd because if we're taking on this many edits, you'd think
> there'd be flushing and compacting going on. There's none.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
