[
https://issues.apache.org/jira/browse/CASSANDRA-4713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13462512#comment-13462512
]
Vijay commented on CASSANDRA-4713:
----------------------------------
Yes the error starts popping up after 0ea28c858e3f693dc44d38cd4306e02049d01ce8
It is simple to reproduce:
1) Use stress to add data to a single node cluster
2) run ./apache-cassandra-1.2.0-beta1-SNAPSHOT/bin/sstableloader -d 127.0.0.1
/var/lib/cassandra/data/Keyspace1/Standard1/
You will see the issue. after this patch or before
0ea28c858e3f693dc44d38cd4306e02049d01ce8 the issue didn't appear.
> -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
