You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "T Jake Luciani (JIRA)" <ji...@apache.org> on 2017/08/23 17:12:00 UTC
[jira] [Assigned] (CASSANDRA-13176) DROP INDEX seemingly doesn't
stop existing Index build
[ https://issues.apache.org/jira/browse/CASSANDRA-13176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
T Jake Luciani reassigned CASSANDRA-13176:
------------------------------------------
Assignee: Dimitar Dimitrov
> DROP INDEX seemingly doesn't stop existing Index build
> ------------------------------------------------------
>
> Key: CASSANDRA-13176
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13176
> Project: Cassandra
> Issue Type: Bug
> Components: Compaction, CQL
> Environment: CentOS Linux, JRE 1.8
> Reporter: Soumya Sanyal
> Assignee: Dimitar Dimitrov
>
> There appears to be an edge case with secondary indexes (non SASI). I originally issued a CREATE INDEX on a column, and upon listening to advice from folks in the #cassandra room, decided against it, and issued a DROP INDEX.
> I didn't check the cluster overnight, but this morning, I found out that our cluster CPU usage was pegged around 80%. Looking at compaction stats, I saw that the index build was still ongoing. We had to restart the entire cluster for the changes to take effect.
> Version: 3.9
--
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