Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Fri, 21 Sep 2012 19:47:08 +1100 (NCT)
From: "Roland Gude (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <918457933.106968.1348217228965.JavaMail.jiratomcat@arcas>
In-Reply-To: <1541472194.86799.1347868387705.JavaMail.jiratomcat@arcas>
Subject: [jira] [Updated] (CASSANDRA-4670) LeveledCompaction destroys
 secondary indexes
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/CASSANDRA-4670?page=3Dcom.atla=
ssian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Roland Gude updated CASSANDRA-4670:
-----------------------------------

    Attachment: compaction2.log

compaction2.log contains a little bit more info. still limited to lines abo=
ut the relevant index - anything that was in the logs near by the compactio=
n stuff.

               =20
> LeveledCompaction destroys secondary indexes
> --------------------------------------------
>
>                 Key: CASSANDRA-4670
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4670
>             Project: Cassandra
>          Issue Type: Bug
>    Affects Versions: 1.1.4, 1.1.5
>            Reporter: Roland Gude
>         Attachments: compaction2.log, compaction.log
>
>
> When LeveledCompactionStrategy is active on a ColumnFamily with an Index =
enabled on TTL Columns, the Index is not working correctly, because the com=
paction is throwing away index data very aggressively.
> Steps to reproduce:
> create a cluster  with a columnfamily with an indexed column and leveled =
compaction:
> create column family CorruptIndex
>   with column_type =3D 'Standard'
>   and comparator =3D 'TimeUUIDType'
>   and default_validation_class =3D 'BytesType'
>   and key_validation_class =3D 'BytesType'
>   and read_repair_chance =3D 0.5
>   and dclocal_read_repair_chance =3D 0.0
>   and gc_grace =3D 864000
>   and min_compaction_threshold =3D 4
>   and max_compaction_threshold =3D 32
>   and replicate_on_write =3D true
>   and compaction_strategy =3D 'org.apache.cassandra.db.compaction.Leveled=
CompactionStrategy'
>   and caching =3D 'NONE'
>   and column_metadata =3D [
>     {column_name : '00000003-0000-1000-0000-000000000000',
>     validation_class : BytesType,
>     index_name : 'idx_corrupt',
>     index_type : 0}];
> in that cf insert expiring data (expiration date should be in the far fut=
ure for the sake of this test)
> query the data by index:
> get CorruptIndex where 00000003-0000-1000-0000-000000000000=3Dutf8(=E2=80=
=98value=E2=80=99)
> see results (should be correct for some time)
> wait for leveled compaction to compact the index
> query the data by index:
> get CorruptIndex where 00000003-0000-1000-0000-000000000000=3Dutf8(=E2=80=
=98value=E2=80=99)
> see results (are empty)
> trigger rebuild index via nodetool
> query the data by index:
> get CorruptIndex where 00000003-0000-1000-0000-000000000000=3Dutf8(=E2=80=
=98value=E2=80=99)
> should be corretc again
> wait for leveled compaction to compact the index
> query the data by index:
> get CorruptIndex where 00000003-0000-1000-0000-000000000000=3Dutf8(=E2=80=
=98value=E2=80=99)
> see results (are empty)
> repeat until bored

--
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