[
https://issues.apache.org/jira/browse/CASSANDRA-6193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13793764#comment-13793764
]
André Cruz commented on CASSANDRA-6193:
---------------------------------------
I was imagining 2 separate long-running processes. No need to fork(). If the
compactor were to fail, the number of pending compactions would increase, as
happens today.
But they would both have to be managed, and should be running.
> Move throughput-heavy activities (repair/compaction) into separate process
> --------------------------------------------------------------------------
>
> Key: CASSANDRA-6193
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6193
> Project: Cassandra
> Issue Type: Wish
> Components: Core
> Reporter: André Cruz
> Priority: Minor
> Labels: ponies
>
> Repairs and compactions are activities that I've seen cause Full GCs. It is
> difficult to optimize the GC for pauseless behaviour when the jvm is
> performing such different functions as serving client requests and processing
> large data files.
> Wouldn't it be possible to separate repairs/compactions into another process
> where Full GCs would not be a problem?
--
This message was sent by Atlassian JIRA
(v6.1#6144)
