[
https://issues.apache.org/jira/browse/CASSANDRA-13801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dimitar Dimitrov updated CASSANDRA-13801:
-----------------------------------------
Attachment: c13801-2.2-testall.png
c13801-3.0-testall.png
c13801-3.11-testall.png
c13801-trunk-testall.png
> CompactionManager sometimes wrongly determines that a background compaction
> is running for a particular table
> -------------------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-13801
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13801
> Project: Cassandra
> Issue Type: Bug
> Components: Compaction
> Reporter: Dimitar Dimitrov
> Assignee: Dimitar Dimitrov
> Priority: Minor
> Attachments: c13801-2.2-testall.png, c13801-3.0-testall.png,
> c13801-3.11-testall.png, c13801-trunk-testall.png
>
>
> Sometimes after writing different rows to a table, then doing a blocking
> flush, if you alter the compaction strategy, then run background compaction
> and wait for it to finish, {{CompactionManager}} may decide that there's an
> ongoing compaction for that same table.
> This may happen even though logs don't indicate that to be the case
> (compaction may still be running for system_schema tables).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
