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 Fri, 07 Sep 2012 20:34:07 GMT


Brandon Williams commented on CASSANDRA-4559:

Every once in a long while you can see this exception:

ERROR 20:30:18,355 Exception in thread Thread[OptionalTasks:1,5,main]
        at org.apache.cassandra.locator.TokenMetadata.removeFromRelocating(
        at org.apache.cassandra.service.StorageService$
        at java.util.concurrent.Executors$
        at java.util.concurrent.FutureTask$Sync.innerRun(
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(
        at java.util.concurrent.ScheduledThreadPoolExecutor$
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(
        at java.util.concurrent.ThreadPoolExecutor$

I suspect this is because we're using the same interval (RING_DELAY) and sometimes they coincide.
 We can just double the relocation removal.
> 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