[
https://issues.apache.org/jira/browse/HBASE-2457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12857678#action_12857678
]
Todd Lipcon commented on HBASE-2457:
------------------------------------
Managed to use the log level servlet to get debug logs of the no-op compactions:
2010-04-15 22:24:05,594 WARN
org.apache.hadoop.hbase.regionserver.MemStoreFlusher: Region
test1,4993900000,1271390277054 has too many store files, putting it back at the
end of the flush queue.
2010-04-15 22:24:05,594 DEBUG
org.apache.hadoop.hbase.regionserver.CompactSplitThread: Compaction requested
for region test1,4993900000,1271390277054/1736416594 because:
regionserver/192.168.42.43:60020.cacheFlusher
2010-04-15 22:24:05,594 INFO org.apache.hadoop.hbase.regionserver.HRegion:
Starting compaction on region test1,4993900000,1271390277054
2010-04-15 22:24:05,597 DEBUG org.apache.hadoop.hbase.regionserver.Store:
Skipped compaction of 1 file; compaction size of actions: 231.5m; Skipped 7
files, size: 242232921
2010-04-15 22:24:05,598 INFO org.apache.hadoop.hbase.regionserver.HRegion:
compaction completed on region test1,4993900000,1271390277054 in 0sec
> RS gets stuck compacting region ad infinitum
> --------------------------------------------
>
> Key: HBASE-2457
> URL: https://issues.apache.org/jira/browse/HBASE-2457
> Project: Hadoop HBase
> Issue Type: Bug
> Affects Versions: 0.20.4
> Reporter: Todd Lipcon
> Priority: Critical
> Attachments: log.gz, stack
>
>
> Testing 0.20_pre_durabil...@934643, I ended up in a state where one region
> server got stuck compacting a single region over and over again forever. This
> was with a special config with very low flush threshold in order to stress
> test flush/compact code.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
