[ https://issues.apache.org/jira/browse/CASSANDRA-8739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14307159#comment-14307159 ]
Benedict commented on CASSANDRA-8739: ------------------------------------- My question is more how this then causes problems, if it fails to markCompacting the candidates it selects? > Don't check for overlap with sstables that have had their start positions > moved in LCS > -------------------------------------------------------------------------------------- > > Key: CASSANDRA-8739 > URL: https://issues.apache.org/jira/browse/CASSANDRA-8739 > Project: Cassandra > Issue Type: Bug > Reporter: Marcus Eriksson > Assignee: Marcus Eriksson > Fix For: 2.1.3 > > Attachments: 0001-8739.patch > > > When picking compaction candidates in LCS, we check that we won't cause any > overlap in the higher level. Problem is that we compare the files that have > had their start positions moved meaning we can cause overlap. We need to also > include the tmplink files when checking this. > Note that in 2.1 overlap is not as big problem as earlier, if adding an > sstable would cause overlap, we send it back to L0 instead, meaning we do a > bit more compaction but we never actually have overlap. -- This message was sent by Atlassian JIRA (v6.3.4#6332)