Return-Path: X-Original-To: apmail-cassandra-user-archive@www.apache.org Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 8F2EC17406 for ; Mon, 19 Jan 2015 14:29:58 +0000 (UTC) Received: (qmail 93308 invoked by uid 500); 19 Jan 2015 14:29:57 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 93261 invoked by uid 500); 19 Jan 2015 14:29:57 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cassandra.apache.org Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 93251 invoked by uid 99); 19 Jan 2015 14:29:57 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 19 Jan 2015 14:29:57 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of artur.kronenberg@openmarket.com designates 83.166.69.119 as permitted sender) Received: from [83.166.69.119] (HELO swordsman.mxtelecom.com) (83.166.69.119) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 19 Jan 2015 14:29:31 +0000 Received: from glide.lon.openmarket.com ([10.9.64.115]) by swordsman.mxtelecom.com with esmtpsa (TLSv1:DHE-RSA-AES128-SHA:128) (Exim 4.84) (envelope-from ) id 1YDDKc-0007qU-GN for user@cassandra.apache.org; Mon, 19 Jan 2015 14:29:30 +0000 Message-ID: <54BD14C8.7000500@openmarket.com> Date: Mon, 19 Jan 2015 14:29:28 +0000 From: Artur Kronenberg User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: user@cassandra.apache.org Subject: Nodetool removenode stuck Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hi, we have had an issue with one of our nodes today: 1. Due to a wrong setup the starting node failed to properly bootstrap. It was shown as UN in the cluster however did not contain any data and we shut it down to fix our configuration issue. 2. We figured we need to remove the node from the cluster before being able to restart it cleanly and have it bootstrap automatically. We used "nodetool removenode UUID" which caused mutliple nodes in our Datacenter to be marked as DOWN for some reason (taken from the log) and a bunch of operations against our cluster to fail. The nodes have come up again and other than a slight heart attack we are fine. However, the removenode operation is now stuck and won't continue. Can anyone recommend on how to proceed safely from here? The node is marked as DL in our cluster. I found https://issues.apache.org/jira/browse/CASSANDRA-6542 however there is no hint on how to handle this properly. Is it save to use the force option here? We don't want to risk the cluster going down for whatever reason again. Thank you! Artur