Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Wed, 13 Feb 2013 16:52:13 +0000 (UTC)
From: =?utf-8?Q?Andr=C3=A9_Cruz_=28JIRA=29?= <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12611096.1349828001154.284992.1360774333821@arcas>
In-Reply-To: <JIRA.12611096.1349828001154@arcas>
References: <JIRA.12611096.1349828001154@arcas>
Subject: [jira] [Commented] (CASSANDRA-4785) Secondary Index Sporadically
 Doesn't Return Rows
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/CASSANDRA-4785?page=3Dcom.atlas=
sian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D=
13577705#comment-13577705 ]=20

Andr=C3=A9 Cruz commented on CASSANDRA-4785:
---------------------------------------

Bug #5225 mentions RuntimeExceptions and CorruptSSTableExceptions, which do=
es not happen to me. This CF in particular is smallish (20k rows, 6MB total=
), so wide rows seem unlikely.=20

Also it seems related to 1.2 and my cluster is on 1.1.5 still.
               =20
> 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
>
> I have a ColumnFamily with caching =3D ALL. I have 2 secondary indexes on=
 it. I have noticed if I query using the secondary index in the where claus=
e, sometimes I get the results and sometimes I don't. Until 2 weeks ago, th=
e caching option on this CF was set to NONE. So, I suspect something happen=
ed in secondary index caching scheme.=20
> 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 beha=
vior looks like cache mistmatch.
> I did a bit research, and found CASSANDRA-4197 that could be related.
> Please advice.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrato=
rs
For more information on JIRA, see: http://www.atlassian.com/software/jira