cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Soumya Sanyal (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-13176) DROP INDEX seemingly doesn't stop existing Index build
Date Thu, 02 Feb 2017 23:21:51 GMT


Soumya Sanyal commented on CASSANDRA-13176:

No, I did not. Is that mandatory? I'm only asking because there might be a case for updating
the document here:

I was following that.

> DROP INDEX seemingly doesn't stop existing Index build
> ------------------------------------------------------
>                 Key: CASSANDRA-13176
>                 URL:
>             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

View raw message