[
https://issues.apache.org/jira/browse/CASSANDRA-4785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
J.B. Langston updated CASSANDRA-4785:
-
Attachment: repro.py
entity_aliases.txt
Reproducible test case. Steps to reproduce:
1) Enable row cache in cassandra.yaml. I used 'row_cache_size_in_mb: 100'.
2) Create schema: 'cassandra-cli entity_aliases.txt'
3) Run reproducible test case (requires pycassa): 'python repro.py'
Script inserts a row into Entity_Aliases table, then queries first by rowId and
then by secondary index. Both queries should return the same row.
5) Sometimes the node needs to be flushed and restarted after the initial
insert before the issue is reproducible.
Expected result:
{code}
Getting by rowId ...
OrderedDict([('alias', u'17SQ0W'), ('aliasType', 'TIP4GQ'), ('entityId',
UUID('9202a758-c605-445d-a67f-30ec8dfebc59')), ('entityType', 'BBN27L')])
Querying with get_indexed_slice ...
OrderedDict([('alias', u'17SQ0W'), ('aliasType', 'TIP4GQ'), ('entityId',
UUID('9202a758-c605-445d-a67f-30ec8dfebc59')), ('entityType', 'BBN27L')])
{code}
Actual Result:
{code}
Getting by rowId ...
OrderedDict([('alias', u'17SQ0W'), ('aliasType', 'TIP4GQ'), ('entityId',
UUID('9202a758-c605-445d-a67f-30ec8dfebc59')), ('entityType', 'BBN27L')])
Querying with get_indexed_slice ...
{code}
Secondary Index Sporadically Doesn't Return Rows
Key: CASSANDRA-4785
URL: https://issues.apache.org/jira/browse/CASSANDRA-4785
Project: Cassandra
Issue Type: Bug
Components: Core
Affects Versions: 1.1.5, 1.1.6
Environment: Ubuntu 10.04
Java 6 Sun
Cassandra 1.1.5 upgraded from 1.1.2 - 1.1.3 - 1.1.5
Reporter: Arya Goudarzi
Attachments: entity_aliases.txt, repro.py
I have a ColumnFamily with caching = ALL. I have 2 secondary indexes on it. I
have noticed if I query using the secondary index in the where clause,
sometimes I get the results and sometimes I don't. Until 2 weeks ago, the
caching option on this CF was set to NONE. So, I suspect something happened
in secondary index caching scheme.
Here are things I tried:
1. I rebuild indexes for that CF on all nodes;
2. I set the caching to KEYS_ONLY and rebuild the index again;
3. I set the caching to NONE and rebuild the index again;
None of the above helped. I suppose the caching still exists as this behavior
looks like cache mistmatch.
I did a bit research, and found CASSANDRA-4197 that could be related.
Please advice.
--
This message was sent by Atlassian JIRA
(v6.1#6144)