cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-4713) -ve Token with M3P
Date Tue, 25 Sep 2012 08:47:07 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-4713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13462575#comment-13462575
] 

Sylvain Lebresne commented on CASSANDRA-4713:
---------------------------------------------

bq. You will see the issue.

Actually, I haven't been able to reproduce the issue on current trunk so far. For 1) I've
tried running stress with 1M keys, 10M keys and with both size tiered and leveled compaction,
but then each time I was able to bulk-load the created sstables without any error.

Is that something you trigger every time? And if so, are you sure that when running the sstableloader
script it doesn't end up picking some older than 1.2.0-beta1 version installed on your system?
                
> -ve Token with M3P
> ------------------
>
>                 Key: CASSANDRA-4713
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4713
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.2.0 beta 1
>            Reporter: Vijay
>            Assignee: Vijay
>             Fix For: 1.2.0
>
>         Attachments: 0001-CASSANDRA-4713.patch
>
>
> Looks like CASSANDRA-4621 has the following code
> {code}
> -        return new LongToken((hash < 0) ? -hash : hash);
> +        return new LongToken(normalize(hash));
>      }
> +    private long normalize(long v)
> +    {
> +        // We exclude the MINIMUM value; see getToken()
> +        return v == Long.MIN_VALUE ? Long.MAX_VALUE : v;
>      }
> {code}
> Causing the following error during bulk loading...
> SSTable first key DecoratedKey(38876769351598, 30393932373730) > last key DecoratedKey(-9223087809888494735,
30393936393438)

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

Mime
View raw message