cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeremy Hanna (Commented) (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-3488) Secondary indexes still around 3 months after deleting them
Date Tue, 15 Nov 2011 18:22:51 GMT


Jeremy Hanna commented on CASSANDRA-3488:

Did a repair on those two nodes.  There aren't any built indexes on any of the column families
on there any longer.  For my part and our cluster, we've fixed the problem, but it sounds
like there is some odd state that is possible.  Maybe we close this issue but keep it as a
data point if other problems show up?
> Secondary indexes still around 3 months after deleting them
> -----------------------------------------------------------
>                 Key: CASSANDRA-3488
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>    Affects Versions: 0.8.4
>            Reporter: Jeremy Hanna
>              Labels: secondary_index
> We had an issue where we lost the data directories of two nodes.  So we re-bootstrapped
those two nodes into the cluster and did the repair.  During the repair, secondary indexes
were built as evidenced both in compactionstats and in the filesystem.  The problem is, we
haven't had secondary indexes on any of our column families for about 3 months now.  The history
there is that we were on 0.7.6, deleted the secondary indexes on that version, and upgraded
to 0.8.4 a bit later.  It bootstrapped and repaired last night and this morning, but it's
been a good 10 hours today of almost exclusively rebuilding secondary indexes that shouldn't
be there.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message