cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nick Bailey (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-4252) Set operation mode to MOVING earlier
Date Thu, 17 May 2012 22:43:07 GMT

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

Nick Bailey commented on CASSANDRA-4252:
----------------------------------------

Ah you are right. I was under the impression we did the RING_DELAY sleep no matter what, but
apparently not.

Regarding the 'fetching new ranges...' log message, we can call setMode multiple times (a
pattern we use for other modes). So we can just call setMode earlier on with a more accurate
log message in addition to the later call.
                
> Set operation mode to MOVING earlier
> ------------------------------------
>
>                 Key: CASSANDRA-4252
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4252
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.1.0
>            Reporter: Nick Bailey
>            Priority: Minor
>
> Right now when moving a node we set the OperationMode only once we've calculated the
necessary ranges to transfer and if there actually are ranges to transfer. Due to the sleep
for ring settling this means there are 30 seconds where the node is moving but the operation
mode isn't set accordingly. Additionally if it turns out no data needs to be transferred then
the move will complete without ever switching the OperationMode to moving.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message