On Thu, Jan 30, 2014 at 3:23 AM, Edward Capriolo wrote:
> Is this only a ByteOrderPartitioner problem?
>
No, see the comments on
https://issues.apache.org/jira/browse/CASSANDRA-6638for more details.
--
Sylvain
>
>
> On Wed, Jan 29, 2014 at 7:34 PM, Tyler Hobbs wrote:
>
>> Ignace,
>>
>> Thanks
Is this only a ByteOrderPartitioner problem?
On Wed, Jan 29, 2014 at 7:34 PM, Tyler Hobbs wrote:
> Ignace,
>
> Thanks for reporting this. I've been able to reproduce the issue with a
> unit test, so I opened
> https://issues.apache.org/jira/browse/CASSANDRA-6638. I'm not 100% sure
> if your f
Ignace,
Thanks for reporting this. I've been able to reproduce the issue with a
unit test, so I opened https://issues.apache.org/jira/browse/CASSANDRA-6638.
I'm not 100% sure if your fix is the correct one, but I should be able to
get it fixed quickly and figure out the full set of cases where a
Got into a problem when testing a vnode setup.
I'm using a byteordered partitioner, linux, code version 2.0.4, replication
factor 1, 4 machine
All goes ok until I run cleanup, and gets worse when adding / decommissioning
nodes.
In my opinion the problem can be found in the SSTableScanner::
KeyS
