cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Fabien Rousseau (Updated) (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-3639) Move streams too many data
Date Thu, 15 Dec 2011 15:52:30 GMT


Fabien Rousseau updated CASSANDRA-3639:

    Attachment: 0001-try-to-fix-move-streaming-too-many-data-unit-tests.patch
> Move streams too many data
> --------------------------
>                 Key: CASSANDRA-3639
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>    Affects Versions: 0.8.7
>            Reporter: Fabien Rousseau
>            Priority: Minor
>         Attachments: 0001-try-to-fix-move-streaming-too-many-data-unit-tests.patch
> During a move operation, we observed that the node streamed most of its data and received
all its data.
> We are running Cassandra 0.8.7 (plus a few patches)
> After reading the code related to "move", we found out that :
>  - in, line 2002 and line 2004 => ranges are returned in a non
ordered collection, but calculateStreamAndFetchRanges() method (line 2011) assume ranges are
sorted, thus, resulting in wider ranges to be fetched/streamed
> We managed to isolate and reproduce this in a unit test.
> We also propose a patch which :
>  - does not rely on any sort
>  - adds a few unit tests (may not be exhaustive...)
> Unit tests are done only for RF=2 and for the "OldNetworkStrategyTopology". For the sake
of simplicity, we've put them in OldNetworkStrategyTopologyTest, but they probably should
be moved.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message