cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Evans (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (CASSANDRA-4559) implement token relocation
Date Tue, 04 Sep 2012 22:01:09 GMT

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

Eric Evans edited comment on CASSANDRA-4559 at 9/5/12 9:00 AM:
---------------------------------------------------------------

Since this is a freeze-dependency, let me provide a bit of a status update:

These patches seemed "mostly" stable prior to merging w/ trunk after CASSANDRA-4383 landed.
 I don't know if the problems since are the result of a faulty merge, a problem with what
was committed for CASSANDRA-4383, or something else entirely (I'm still looking into it).

I say "mostly" stable because occasionally one node would seem to miss the {{NORMAL}} sent
by the destination node after a successful relocation, and so that nodes idea of the state
of the ring would differ from the rest of the cluster.  I'm still looking into this, or I
will be after sorting out the new spate of issues (see above).

Most of the challenges here have related to network concurrency, so if you wish to test, you
really need to use the shuffle utility in order to set more than one in motion at once.  The
shuffle tool isn't quite done yet either, but (if interested )you can checkout at https://github.com/acunu/cassandra/tree/p/4443/060_shuffle_utility
(which includes the token relocation).
                
      was (Author: urandom):
    Since this is a freeze-dependency, let me provide a bit of a status update:

These patches seemed "mostly" stable prior to merging w/ trunk after CASSANDRA-4383 landed.
 I don't know if the problems since are the result of a faulty merge, a problem with what
was committed for CASSANDRA-4383, or something else entirely (I'm still looking into it).

I say "mostly" stable because occasionally one node would seem to miss the {{NORMAL}} sent
by the destination node after a successful relocation, and so that nodes idea of the state
of the ring would differ from the rest of the cluster.  I'm still looking into this, or I
will be after sorting out the new spate of issues (see above).

Most of the challenges here have related to network concurrency, so you if wish to test, you
really need to use the shuffle utility in order to set more than one in motion at once.  The
shuffle tool isn't quite done yet either, but (if interested )you can checkout at https://github.com/acunu/cassandra/tree/p/4443/060_shuffle_utility
(which includes the token relocation).
                  
> implement token relocation
> --------------------------
>
>                 Key: CASSANDRA-4559
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4559
>             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
>
>
> 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|https://github.com/acunu/cassandra/compare/top-bases/p/4443/010_refactor_range_move...p/4443/010_refactor_range_move]|[010_refactor_range_move.patch|https://github.com/acunu/cassandra/compare/top-bases/p/4443/010_refactor_range_move...p/4443/010_refactor_range_move.diff]|No
Description|
> |[020_calculate_pending|https://github.com/acunu/cassandra/compare/top-bases/p/4443/020_calculate_pending...p/4443/020_calculate_pending]|[020_calculate_pending.patch|https://github.com/acunu/cassandra/compare/top-bases/p/4443/020_calculate_pending...p/4443/020_calculate_pending.diff]|No
Description|
> |[030_relocate_token|https://github.com/acunu/cassandra/compare/top-bases/p/4443/030_relocate_token...p/4443/030_relocate_token]|[030_relocate_token.patch|https://github.com/acunu/cassandra/compare/top-bases/p/4443/030_relocate_token...p/4443/030_relocate_token.diff]|No
Description|
> |[040_tests|https://github.com/acunu/cassandra/compare/top-bases/p/4443/040_tests...p/4443/040_tests]|[040_tests.patch|https://github.com/acunu/cassandra/compare/top-bases/p/4443/040_tests...p/4443/040_tests.diff]|No
Description|
> ----
> _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: http://www.atlassian.com/software/jira

Mime
View raw message