cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karl Mueller (JIRA)" <>
Subject [jira] Updated: (CASSANDRA-1884) sstable2json / sstablekeys should verify key order in -Data and -Index files
Date Sat, 18 Dec 2010 21:42:01 GMT


Karl Mueller updated CASSANDRA-1884:

    Attachment: c0.7-ordered-key-check.txt

This patches to keep the last key seen and throw an exception if an earlier
key is seen subsequently.

> sstable2json / sstablekeys should verify key order in -Data and -Index files
> ----------------------------------------------------------------------------
>                 Key: CASSANDRA-1884
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Tools
>    Affects Versions: 0.7.0
>            Reporter: Karl Mueller
>            Priority: Minor
>         Attachments: c0.7-ordered-key-check.txt
> Some cassandra users use sstable2json and sstablekeys to check -Data and -Index files
for integrity.  For example, if compaction fails, you can find out which files are causing
the compaction to fail because they're corrupt.  One type of corruption that can happen in
both -Data and -Index files are keys getting out of order.  (This shouldn't happen, but it
can)  Cassandra catches this error during compaction, but both tools didn't catch it.  
> This small patch simply causes an IO Exception during export if it finds out of order
> Some further work on it may make this optional with a command-line switch - it may be
useful to export the data to json even though it's out of order to manually play it back,
or have another script re-order it. 

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message