cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joshua McKenzie (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-13801) CompactionManager sometimes wrongly determines that a background compaction is running for a particular table
Date Tue, 03 Oct 2017 13:47:00 GMT

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

Joshua McKenzie updated CASSANDRA-13801:
----------------------------------------
    Priority: Minor  (was: Major)

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


Mime
View raw message