cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sam Tunnicliffe (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-6272) sstableloader data distribution is broken since 1.2.7
Date Wed, 30 Oct 2013 21:09:30 GMT

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

Sam Tunnicliffe updated CASSANDRA-6272:
---------------------------------------

    Attachment: SSTableReaderTest-for-2.0.patch
                SSTableReaderTest-for-trunk.patch

Patches with SSTableReaderTest updated for 2.0 & trunk

> sstableloader data distribution is broken since 1.2.7
> -----------------------------------------------------
>
>                 Key: CASSANDRA-6272
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6272
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Tools
>            Reporter: Sam Tunnicliffe
>            Assignee: Sam Tunnicliffe
>            Priority: Minor
>             Fix For: 1.2.12
>
>         Attachments: 0001-CASSANDRA-6272-Load-or-build-a-real-IndexSummary-in-.patch,
SSTableReaderTest-for-2.0.patch, SSTableReaderTest-for-trunk.patch
>
>
> Running sstableloader on 1.2.10+ results in radically different distribution compared
with earlier versions. It looks as though the 'bare-bones' IndexSummary created in SSTR.loadForBatch
is the cause (CASSANDRA-5555); because it contains only a single entry, we end up with the
wrong segment of the index file in SSTR.getPosition (its position is always 0),  so only the
first segment of the index file is considered when searching for the range's position.
> This doesn't affect  2.0/trunk



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message