[ https://issues.apache.org/jira/browse/CASSANDRA-13176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15849669#comment-15849669 ]
Romain Hardouin commented on CASSANDRA-13176: --------------------------------------------- Did you try {{nodetool stop INDEX_BUILD}} prior to restart nodes? > 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 > > 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.3.15#6346)