You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Charles (JIRA)" <ji...@apache.org> on 2015/03/24 07:39:52 UTC

[jira] [Created] (CASSANDRA-9026) Garbage in the sstable of the secondary index

Charles created CASSANDRA-9026:
----------------------------------

             Summary: 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)