Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Date: Fri, 2 Dec 2011 10:07:42 -0800 (PST)
From: huyle <huyle@springpartners.com>
To: cassandra-user@incubator.apache.org
Message-ID: <1322849262098-7055647.post@n2.nabble.com>
In-Reply-To: 
 <CAAafH9Szfox8v7YSXWTpVD+mJiso=mWkY0sY8_Khgnh4NbsPCg@mail.gmail.com>
References: <1322763963291-7051526.post@n2.nabble.com>
 <CAAafH9Q_nFVzFjcaxgXBWyfGSqdbnrXvo2Zwte5udO_=ixKQRw@mail.gmail.com>
 <1322766653905-7051701.post@n2.nabble.com>
 <CAAafH9Szfox8v7YSXWTpVD+mJiso=mWkY0sY8_Khgnh4NbsPCg@mail.gmail.com>
Subject: Re: decommissioned not show being gossipped
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

In our case, we need to execute "unsafeAssassinateEndpoint" from
https://issues.apache.org/jira/browse/CASSANDRA-3337.    How do we go about
applying the patch attached to CASSANDRA-3337?  We always used the binary
distribution; never had to compile cassandra; so we are not sure of the
proper way to apply the patch and compile new binary.  We currently running
1.0.3.

 Thanks!

Huy


unsafeAssassinateEndpoint


Brandon Williams wrote
> 
> On Thu, Dec 1, 2011 at 1:10 PM, huyle &lt;huyle@&gt; wrote:
>> The clocks are very sync'ed between the nodes as they have ntp running
>> hitting our time servers.
> 
> Maybe they weren't 3 days after the token left, which
> https://issues.apache.org/jira/browse/CASSANDRA-2961 requires.
> 
> If a node sees the token you can removetoken it, otherwise you'll need
> https://issues.apache.org/jira/browse/CASSANDRA-3337
> 
> -Brandon
> 


--
View this message in context: http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/decommissioned-nodes-still-being-gossipped-tp7051526p7055647.html
Sent from the cassandra-user@incubator.apache.org mailing list archive at Nabble.com.