From user-return-29343-apmail-cassandra-user-archive=cassandra.apache.org@cassandra.apache.org Fri Oct 5 11:48:27 2012 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 893D1DF27 for ; Fri, 5 Oct 2012 11:48:27 +0000 (UTC) Received: (qmail 14431 invoked by uid 500); 5 Oct 2012 11:48:25 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 13983 invoked by uid 500); 5 Oct 2012 11:48:24 -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 13957 invoked by uid 99); 5 Oct 2012 11:48:23 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 Oct 2012 11:48:23 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [209.85.217.172] (HELO mail-lb0-f172.google.com) (209.85.217.172) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 Oct 2012 11:48:15 +0000 Received: by mail-lb0-f172.google.com with SMTP id k13so1414413lbo.31 for ; Fri, 05 Oct 2012 04:47:53 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:x-gm-message-state; bh=gU2dEif7q4fHmfqgoYsxb+KMZth64LZmRSbuwENE4ng=; b=Xp2/wxZ2sRP6WaORripsUa9naaKNrqDFAeqfBy0Lf4T0375CEkqQnTmNhON91RH9gv yzdRTnCZ0EpBAu1H9vtfLhw59AgPXm0m3jMUUt1+18Mbt7XYmZcHMuUXC0ki47jQGGjR rpxjZ/cVg7LugXwB0GOFeCZ+wni7nbvvsbc/SkoS2X2dZccra+Z6Swk5yZ7voVhG9/YF 8DBuSeABOQ5p+re1KVpuZAn+mzdOBmSSnl0iO9Rh6Yp1SFRMMtMBO7IngpgEjgN1OH/N MMoNsttv1RUfN1w2X9NCf63bIsv5a8wkL054XaXMSCNPhqDQf58ql99LkG+Cty5dw6Zi ijsw== Received: by 10.112.43.34 with SMTP id t2mr3149761lbl.109.1349437672986; Fri, 05 Oct 2012 04:47:52 -0700 (PDT) Received: from [192.168.2.92] (81-94-164-42.customer.itmastaren.net. [81.94.164.42]) by mx.google.com with ESMTPS id sj3sm2087865lab.2.2012.10.05.04.47.51 (version=SSLv3 cipher=OTHER); Fri, 05 Oct 2012 04:47:52 -0700 (PDT) Message-ID: <506EC8E5.5090501@sitevision.se> Date: Fri, 05 Oct 2012 13:47:49 +0200 From: Fredrik User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120907 Thunderbird/15.0.1 MIME-Version: 1.0 To: user@cassandra.apache.org Subject: Re: Remove node from cluster and have it run as a single node cluster by itself References: <0E566740EC90304EB9C1C25261C4B8C7CEC4C9@WTPCPMBMEM08.ams.bnymellon.net> In-Reply-To: <0E566740EC90304EB9C1C25261C4B8C7CEC4C9@WTPCPMBMEM08.ams.bnymellon.net> Content-Type: multipart/alternative; boundary="------------080603080009050504050805" X-Gm-Message-State: ALoCoQnLywN7OhaQXShJtDtOIignKfLDk4Z81rSrvYL0jy+uNyor5R+3DmUD6OY0pwommLrvw1Tq X-Virus-Checked: Checked by ClamAV on apache.org This is a multi-part message in MIME format. --------------080603080009050504050805 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit I guess that the other nodes still gossips about the removed node. The node isn't removed from gossiper in the cluster until some amount of time have elapsed. My guess is that you haven't changed the cluster_name property in the cassandra.yaml on the removed node. Xu, Zaili skrev 2012-09-28 20:53: > > I have an existing Cassandra Cluster. I removed a node from the > cluster. Then I decommissioned the removed node, stopped it, updated > its config so that it only has itself as the seed and in the > cassandra-topology.properties file, even deleted the data, commitlog, > and saved_caches. But as soon as I start it backup it is able to join > back to the cluster. How does this node know the information of the > existing cluster and was able to join it ? > --------------080603080009050504050805 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit
I guess that the other nodes still gossips about the removed node. The node isn't removed from gossiper in the cluster until some amount of time have elapsed. My guess is that you haven't changed the cluster_name property  in the cassandra.yaml on the removed node.


Xu, Zaili skrev 2012-09-28 20:53:

I have an existing Cassandra Cluster. I removed a node from the cluster. Then I decommissioned the removed node, stopped it,  updated its config so that it only has itself as the seed and in the cassandra-topology.properties file, even deleted the data, commitlog, and saved_caches. But as soon as I start it backup it is able to join back to the cluster.  How does this node know the information of the existing cluster and was able to join it ?


--------------080603080009050504050805--