Return-Path: Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: (qmail 92179 invoked from network); 23 Dec 2010 20:21:10 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 23 Dec 2010 20:21:10 -0000 Received: (qmail 95610 invoked by uid 500); 23 Dec 2010 20:21:10 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 95585 invoked by uid 500); 23 Dec 2010 20:21:10 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 95575 invoked by uid 99); 23 Dec 2010 20:21:10 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 23 Dec 2010 20:21:10 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 23 Dec 2010 20:21:07 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id oBNKKkt5017390 for ; Thu, 23 Dec 2010 20:20:46 GMT Message-ID: <30842936.2471293135646191.JavaMail.jira@thor> Date: Thu, 23 Dec 2010 15:20:46 -0500 (EST) From: "Nick Bailey (JIRA)" To: commits@cassandra.apache.org Subject: [jira] Created: (CASSANDRA-1900) Make removetoken force always work MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org Make removetoken force always work ---------------------------------- Key: CASSANDRA-1900 URL: https://issues.apache.org/jira/browse/CASSANDRA-1900 Project: Cassandra Issue Type: Improvement Components: Tools Affects Versions: 0.7.0 rc 2, 0.7.0 Reporter: Nick Bailey Fix For: 0.7.1 The 'removetoken force' command was intended for forcing a removal to complete when the removal stalls for some reason. The most likely reason being a streaming failure causing the node to wait forever for streams to complete. The command should be updated so that it can force a removal in any case. For example a node that was decommissioned but killed before a LEFT status was broadcasted. This leaves the node in a permanent 'leaving' state. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.