[ https://issues.apache.org/jira/browse/CASSANDRA-4174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13257821#comment-13257821 ]
Jonathan Ellis commented on CASSANDRA-4174: ------------------------------------------- Devil's advocate for the status quo: starting compaction as soon as I have one sstable to work on might "smooth out" the workload more. (If we finish the first compaction before the next is available, then great; if we don't, then they'll stack up and we'll do something closer to the "all at once" approach.) Thoughts? > Unnecessary compaction happens when streaming > --------------------------------------------- > > Key: CASSANDRA-4174 > URL: https://issues.apache.org/jira/browse/CASSANDRA-4174 > Project: Cassandra > Issue Type: Improvement > Components: Core > Affects Versions: 1.0.0 > Reporter: Yuki Morishita > Assignee: Yuki Morishita > Priority: Minor > Fix For: 1.0.10 > > Attachments: 4174-1.0.txt > > > When streaming session finishes, streamed sstabls are added to CFS one by one > using > ColumnFamilyStore#addSSTable(https://github.com/apache/cassandra/blob/cassandra-1.0.9/src/java/org/apache/cassandra/streaming/StreamInSession.java#L141). > This method submits compaction in > background(https://github.com/apache/cassandra/blob/cassandra-1.0.9/src/java/org/apache/cassandra/db/ColumnFamilyStore.java#L946), > and end up with unnecessary compaction tasks behind. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira