cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Philip Thompson (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CASSANDRA-9026) Garbage in the sstable of the secondary index
Date Wed, 25 Mar 2015 15:41:54 GMT

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

Philip Thompson resolved CASSANDRA-9026.
----------------------------------------
    Resolution: Duplicate

As Carl said, it does look like this is fixed in 3.0, and will not be backported. Until then,
an alternate solution is to drop and rebuild the index.

> Garbage in the sstable of the secondary index
> ---------------------------------------------
>
>                 Key: CASSANDRA-9026
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9026
>             Project: Cassandra
>          Issue Type: Bug
>         Environment: CentOS 6.5
>            Reporter: Charles
>
> We create a secondary index for a specific column.
> After running a few months, by using sstable2json tool, we found there are some unknown
keys which we've never assigned are stored in the sstable of the secondary index. The key
value is incremental hexbyte, for example, 55012157, 55012158.
> It can not be removed by nodetool repair/compact/cleanup.
> When the sstable of the secondary index become larger, the read performance is dropped.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message