cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brandon Williams (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-4559) implement token relocation
Date Wed, 12 Sep 2012 00:35:07 GMT


Brandon Williams commented on CASSANDRA-4559:

bq. Updated patch fixes that, but there's still something wrong, however nodes at least stream
out now.

I take it back that something is still wrong, replicas are all going to right places now.
 The remaining problems that I see are the aforementioned NPE (very rare) and sometimes I
see nodes incorrectly fall back to generation comparison on token conflicts instead of relocating,
leading to different views of the ring on different nodes.  I'm not really sure what is causing
either of these yet.
> implement token relocation
> --------------------------
>                 Key: CASSANDRA-4559
>                 URL:
>             Project: Cassandra
>          Issue Type: Sub-task
>          Components: Core, Tools
>    Affects Versions: 1.2.0 beta 1
>            Reporter: Eric Evans
>            Assignee: Eric Evans
>              Labels: vnodes
>             Fix For: 1.2.0 beta 1
>         Attachments: 4559.txt
> Whatever the specifics of a _shuffle_ (see CASSANDRA-4443), it will be necessary to relocate
a range from one node to another.
> _Edit0: Linked in new patch containing tests._
> ----
> h3. Patches
> ||Compare||Raw diff||Description||
> |[010_refactor_range_move|]|[010_refactor_range_move.patch|]|No
> |[020_calculate_pending|]|[020_calculate_pending.patch|]|No
> |[030_relocate_token|]|[030_relocate_token.patch|]|No
> |[040_tests|]|[040_tests.patch|]|No
> ----
> _Note: These are branches managed with TopGit. If you are applying the patch output manually,
you will either need to filter the TopGit metadata files (i.e. {{wget -O - <url> | filterdiff
-x*.topdeps -x*.topmsg | patch -p1}}), or remove them afterward ({{rm .topmsg .topdeps}})._

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:

View raw message