You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2013/10/13 20:35:41 UTC

[jira] [Updated] (CASSANDRA-6193) Move throughput-heavy activities (repair/compaction) into separate process

     [ https://issues.apache.org/jira/browse/CASSANDRA-6193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Ellis updated CASSANDRA-6193:
--------------------------------------

    Priority: Minor  (was: Major)
      Labels: ponies  (was: )

It's not crazy, but it's a lot of code to write.

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