Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Mon, 11 Apr 2011 17:01:05 +0000 (UTC)
From: "Nick Bailey (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: 
 <172283619.49504.1302541265843.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Created] (CASSANDRA-2448) Remove loadbalance command
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

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