You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Dimitar Dimitrov (JIRA)" <ji...@apache.org> on 2017/08/25 11:52:00 UTC
[jira] [Created] (CASSANDRA-13801) CompactionManager sometimes
wrongly determines that a background compaction is running for a particular
table
Dimitar Dimitrov created CASSANDRA-13801:
--------------------------------------------
Summary: 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
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: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org