[
https://issues.apache.org/jira/browse/CASSANDRA-5554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeremiah Jordan updated CASSANDRA-5554:
---------------------------------------
Fix Version/s: 1.2.5
> Growing pending compactions
> ---------------------------
>
> Key: CASSANDRA-5554
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5554
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.2.4
> Reporter: Oleg Anastasyev
> Assignee: Oleg Anastasyev
> Fix For: 1.2.5
>
> Attachments: patch.diff, pending_compactions_fixed.png
>
>
> I noticed on one of our new cassandra production server, that "pending
> compactions" number is steadily growing. The cluster is under low write load,
> so "compactions are not keeping up" was not the case.
> A quick investigation shown, that compactions are stopping far before all
> pending tasks are completed. I also found, that if concurrent_compactors=1,
> background compactions are not happening at all.
> The bug is in BackgroundCompactionTask rescheduling logic. The executor pool
> "room control" code in CompactionManager.submitBackground() does not
> reschedule next background cycle, if executor.getActiveCount reach maximun
> pool size, so it is lost forever.
> So I patched it to always schedule single background cycle, regardless of the
> free room in executor pool.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
