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 A782511BF9 for ; Tue, 5 Aug 2014 00:57:27 +0000 (UTC) Received: (qmail 68424 invoked by uid 500); 5 Aug 2014 00:57:25 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 68384 invoked by uid 500); 5 Aug 2014 00:57:25 -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 68374 invoked by uid 99); 5 Aug 2014 00:57:24 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Aug 2014 00:57:24 +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.213.45] (HELO mail-yh0-f45.google.com) (209.85.213.45) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Aug 2014 00:57:20 +0000 Received: by mail-yh0-f45.google.com with SMTP id 29so163690yhl.18 for ; Mon, 04 Aug 2014 17:56:59 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:references:from:content-type:in-reply-to :message-id:date:to:content-transfer-encoding:mime-version; bh=SjFMdT1bMWXh3u0KOybTyYRZNVCtltzBf2tLEZf14nY=; b=aDj3zCOB7Lf9g54hUXMBy2YPxebOv8kXVy6SRk5e8nVe+D6Pv/bVXgWLyjhm5+foy9 WzZgsnRX/HHthdsFKyhGqlPGkHOxiWV+U8NBm4PCutACxRyJlqjnROHJ9x8n9465XgbM pWRgWpNCUVsRvFtVDbJElZZxHe0pv6kxPCaFW0C8hnQ4+bh7s0X85CiCGhN6qt762mId SY1e4BNAwX/74EgSuXlPUkZsSbKDe74HEphEoTnQ0FP3tBdaYVYw9qr6ufLqSoUgM4Rg FlxEKnKfwlf1qFmPAYBowkw1M9pgZrbH6syZ5wjO8pNRoq2tvzMUQMfql3sgTrcM42n4 GbGg== X-Gm-Message-State: ALoCoQlcNa0SyoO9g6QeUqOqAUQSjBP7WvTG4vNoXOPVnoPO8mZuCX2obxNrl3AlEjhpQw+qDiYv X-Received: by 10.236.63.164 with SMTP id a24mr370535yhd.85.1407200219228; Mon, 04 Aug 2014 17:56:59 -0700 (PDT) Received: from [10.1.62.177] ([166.205.65.132]) by mx.google.com with ESMTPSA id g30sm270783yhn.46.2014.08.04.17.56.57 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 04 Aug 2014 17:56:57 -0700 (PDT) Subject: Re: How to get rid of stale info in gossip References: <5754C999-ABFA-47D1-A23A-EC8A310993DC@rahul.be> <2F5B8CD9-31C9-4B56-A9C8-7516A1792C9D@rahul.be> From: Rahul Neelakantan Content-Type: multipart/alternative; boundary=Apple-Mail-BBFC1275-3CE0-4FA4-8BF6-B9CA5F79B3B6 X-Mailer: iPhone Mail (11D257) In-Reply-To: Message-Id: <964EDE0A-48B4-4A09-B0E3-37142DA78767@rahul.be> Date: Mon, 4 Aug 2014 20:56:51 -0400 To: "user@cassandra.apache.org" Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (1.0) X-Virus-Checked: Checked by ClamAV on apache.org --Apple-Mail-BBFC1275-3CE0-4FA4-8BF6-B9CA5F79B3B6 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable It no longer shows up, but I will definitely investigate that option. What e= xactly does it do? Rahul Neelakantan > On Aug 4, 2014, at 7:49 PM, Patricia Gorla wr= ote: >=20 > Rahul, >=20 > If the removed node is still showing up in gossip state, you can remove it= with 'unsafeAssassinate' via a JMX tool such as jconsole or jmxterm. >=20 >=20 >> On Fri, Jul 25, 2014 at 6:10 AM, Rahul Neelakantan wrote= : >> Yes, and this is a really old version of casandra 1.0.8. >>=20 >>=20 >> Rahul Neelakantan >> 678-451-4545 >>=20 >>> On Jul 25, 2014, at 7:29 AM, Mark Reddy wrote: >>>=20 >>> After removing a node, it's information can persist in the Gossiper for u= p to 3 days, after which time it should be removed.=20 >>>=20 >>> Are you having issues with a removed node state persisting for longer? >>>=20 >>>=20 >>> Mark >>>=20 >>>=20 >>>> On Fri, Jul 25, 2014 at 11:33 AM, Rahul Neelakantan wr= ote: >>>> Is there a way to get rid of stale information that shows up for remove= d/dead nodes in gossip, without a complete cluster bounce? >>>>=20 >>>> Rahul Neelakantan >=20 >=20 >=20 > --=20 > Patricia Gorla > @patriciagorla >=20 > Consultant > Apache Cassandra Consulting > http://www.thelastpickle.com --Apple-Mail-BBFC1275-3CE0-4FA4-8BF6-B9CA5F79B3B6 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit
It no longer shows up, but I will definitely investigate that option. What exactly does it do?

Rahul Neelakantan

On Aug 4, 2014, at 7:49 PM, Patricia Gorla <patricia@thelastpickle.com> wrote:

Rahul,

If the removed node is still showing up in gossip state, you can remove it with 'unsafeAssassinate' via a JMX tool such as jconsole or jmxterm.


On Fri, Jul 25, 2014 at 6:10 AM, Rahul Neelakantan <rahul@rahul.be> wrote:
Yes, and this is a really old version of casandra 1.0.8.


Rahul Neelakantan

On Jul 25, 2014, at 7:29 AM, Mark Reddy <mark.reddy@boxever.com> wrote:

After removing a node, it's information can persist in the Gossiper for up to 3 days, after which time it should be removed. 

Are you having issues with a removed node state persisting for longer?


Mark


On Fri, Jul 25, 2014 at 11:33 AM, Rahul Neelakantan <rahul@rahul.be> wrote:
Is there a way to get rid of stale information that shows up for removed/dead nodes in gossip, without a complete cluster bounce?

Rahul Neelakantan





--
Patricia Gorla
@patriciagorla

Consultant
Apache Cassandra Consulting
--Apple-Mail-BBFC1275-3CE0-4FA4-8BF6-B9CA5F79B3B6--