You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Nick Bailey (JIRA)" <ji...@apache.org> on 2011/04/11 19:01:05 UTC
[jira] [Created] (CASSANDRA-2448) Remove loadbalance command
Remove loadbalance command
--------------------------
Key: CASSANDRA-2448
URL: https://issues.apache.org/jira/browse/CASSANDRA-2448
Project: Cassandra
Issue Type: Bug
Components: Tools
Affects Versions: 0.8
Reporter: Nick Bailey
Assignee: Nick Bailey
Priority: Minor
Fix For: 0.8
Attachments: 0001-Remove-loadbalance-command-from-nodetool.patch
With the update to how the move command works, the loadbalance command is even less useful that it was previously. The loadbalance command now calculates the token it is going to move to before it leaves which means it isn't considering the load it is giving away. Given that, I think we should just remove the loadbalance command entirely. Anyone who wants to do an old style loadbalance can just do decommission then bootstrap.
This is a minor change, and honestly I think it might count as a 'bug' so I think we should squeeze it into 0.8, post-freeze.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-2448) Remove loadbalance command
Posted by "Cathy Daw (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13022541#comment-13022541 ]
Cathy Daw commented on CASSANDRA-2448:
--------------------------------------
Not sure how documentation gets updated, but we still mention using the loadbalance command on the wiki:
http://wiki.apache.org/cassandra/Operations#Moving_or_Removing_nodes
> Remove loadbalance command
> --------------------------
>
> Key: CASSANDRA-2448
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2448
> Project: Cassandra
> Issue Type: Bug
> Components: Tools
> Affects Versions: 0.8 beta 1
> Reporter: Nick Bailey
> Assignee: Nick Bailey
> Priority: Minor
> Fix For: 0.8 beta 1
>
> Attachments: 0001-Remove-loadbalance-command-from-nodetool.patch
>
>
> With the update to how the move command works, the loadbalance command is even less useful that it was previously. The loadbalance command now calculates the token it is going to move to before it leaves which means it isn't considering the load it is giving away. Given that, I think we should just remove the loadbalance command entirely. Anyone who wants to do an old style loadbalance can just do decommission then bootstrap.
> This is a minor change, and honestly I think it might count as a 'bug' so I think we should squeeze it into 0.8, post-freeze.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-2448) Remove loadbalance command
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13018530#comment-13018530 ]
Jonathan Ellis commented on CASSANDRA-2448:
-------------------------------------------
merging to trunk is asynchronous but will happen
> Remove loadbalance command
> --------------------------
>
> Key: CASSANDRA-2448
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2448
> Project: Cassandra
> Issue Type: Bug
> Components: Tools
> Affects Versions: 0.8
> Reporter: Nick Bailey
> Assignee: Nick Bailey
> Priority: Minor
> Fix For: 0.8
>
> Attachments: 0001-Remove-loadbalance-command-from-nodetool.patch
>
>
> With the update to how the move command works, the loadbalance command is even less useful that it was previously. The loadbalance command now calculates the token it is going to move to before it leaves which means it isn't considering the load it is giving away. Given that, I think we should just remove the loadbalance command entirely. Anyone who wants to do an old style loadbalance can just do decommission then bootstrap.
> This is a minor change, and honestly I think it might count as a 'bug' so I think we should squeeze it into 0.8, post-freeze.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-2448) Remove loadbalance command
Posted by "Nick Bailey (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13022547#comment-13022547 ]
Nick Bailey commented on CASSANDRA-2448:
----------------------------------------
Updated the wiki to indicate that the loadbalance command is only available in versions 0.7.* and lower.
> Remove loadbalance command
> --------------------------
>
> Key: CASSANDRA-2448
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2448
> Project: Cassandra
> Issue Type: Bug
> Components: Tools
> Affects Versions: 0.8 beta 1
> Reporter: Nick Bailey
> Assignee: Nick Bailey
> Priority: Minor
> Fix For: 0.8 beta 1
>
> Attachments: 0001-Remove-loadbalance-command-from-nodetool.patch
>
>
> With the update to how the move command works, the loadbalance command is even less useful that it was previously. The loadbalance command now calculates the token it is going to move to before it leaves which means it isn't considering the load it is giving away. Given that, I think we should just remove the loadbalance command entirely. Anyone who wants to do an old style loadbalance can just do decommission then bootstrap.
> This is a minor change, and honestly I think it might count as a 'bug' so I think we should squeeze it into 0.8, post-freeze.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-2448) Remove loadbalance command
Posted by "Nick Bailey (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nick Bailey updated CASSANDRA-2448:
-----------------------------------
Attachment: 0001-Remove-loadbalance-command-from-nodetool.patch
> Remove loadbalance command
> --------------------------
>
> Key: CASSANDRA-2448
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2448
> Project: Cassandra
> Issue Type: Bug
> Components: Tools
> Affects Versions: 0.8
> Reporter: Nick Bailey
> Assignee: Nick Bailey
> Priority: Minor
> Fix For: 0.8
>
> Attachments: 0001-Remove-loadbalance-command-from-nodetool.patch
>
>
> With the update to how the move command works, the loadbalance command is even less useful that it was previously. The loadbalance command now calculates the token it is going to move to before it leaves which means it isn't considering the load it is giving away. Given that, I think we should just remove the loadbalance command entirely. Anyone who wants to do an old style loadbalance can just do decommission then bootstrap.
> This is a minor change, and honestly I think it might count as a 'bug' so I think we should squeeze it into 0.8, post-freeze.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-2448) Remove loadbalance command
Posted by "Nick Bailey (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13018514#comment-13018514 ]
Nick Bailey commented on CASSANDRA-2448:
----------------------------------------
this should also be applied to trunk
> Remove loadbalance command
> --------------------------
>
> Key: CASSANDRA-2448
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2448
> Project: Cassandra
> Issue Type: Bug
> Components: Tools
> Affects Versions: 0.8
> Reporter: Nick Bailey
> Assignee: Nick Bailey
> Priority: Minor
> Fix For: 0.8
>
> Attachments: 0001-Remove-loadbalance-command-from-nodetool.patch
>
>
> With the update to how the move command works, the loadbalance command is even less useful that it was previously. The loadbalance command now calculates the token it is going to move to before it leaves which means it isn't considering the load it is giving away. Given that, I think we should just remove the loadbalance command entirely. Anyone who wants to do an old style loadbalance can just do decommission then bootstrap.
> This is a minor change, and honestly I think it might count as a 'bug' so I think we should squeeze it into 0.8, post-freeze.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira