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 2E154DD8D for ; Wed, 15 Aug 2012 04:58:59 +0000 (UTC) Received: (qmail 33453 invoked by uid 500); 15 Aug 2012 04:58:56 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 33415 invoked by uid 500); 15 Aug 2012 04:58:56 -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 33397 invoked by uid 99); 15 Aug 2012 04:58:55 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 15 Aug 2012 04:58:55 +0000 X-ASF-Spam-Status: No, hits=2.4 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,FSL_RCVD_USER,HK_RANDOM_ENVFROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of teddyyyy123@gmail.com designates 209.85.216.51 as permitted sender) Received: from [209.85.216.51] (HELO mail-qa0-f51.google.com) (209.85.216.51) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 15 Aug 2012 04:58:51 +0000 Received: by qadz3 with SMTP id z3so1003981qad.10 for ; Tue, 14 Aug 2012 21:58:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=ni/lRAR3dl7wp5uNMwjTOabr2pTKid8uZSw3MyTd+9s=; b=OFgu8Yjmj+/AFgiub3TvWnCC8Exg0h/wsMizP7gnKwNOwTdoD3b8kPS1w8IniGCAt4 98jOLVD9CQZUlIjb9Jfi5y410z0nrEPOfvNDQc7XKafgReXkgCUDmnjSGr0ZvN6xfaGi 7CoaKF67v8x1QENrudtPaN8aLyo7JeWGaEGDkWsN265apjCZBA3mXJ2lXiDxdbfvzsnB +uTHfmE4h6Gz3K1peji/4YnqklE7Bt9Y2s1AgsV0q0qYY9SRkHNY5ThxAVqBv97TF6In OMa9v5Hr1diABouvh+Vb27/qOC1FF3XoNmfWPCm+uoARVzQO+vlYpk7Tjcgz4tZ7wzWC iNLw== MIME-Version: 1.0 Received: by 10.224.213.194 with SMTP id gx2mr38109299qab.11.1345006710366; Tue, 14 Aug 2012 21:58:30 -0700 (PDT) Received: by 10.49.41.72 with HTTP; Tue, 14 Aug 2012 21:58:30 -0700 (PDT) Received: by 10.49.41.72 with HTTP; Tue, 14 Aug 2012 21:58:30 -0700 (PDT) In-Reply-To: References: Date: Tue, 14 Aug 2012 21:58:30 -0700 Message-ID: Subject: Re: replace dead node? " token -1 " From: Yang To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=20cf3005149831200c04c746c7a0 X-Virus-Checked: Checked by ClamAV on apache.org --20cf3005149831200c04c746c7a0 Content-Type: text/plain; charset=ISO-8859-1 thanks Aaron, it has been a while since i last checked the code, I'll read it to understand it more On Aug 14, 2012 8:48 PM, "aaron morton" wrote: > Using this method, when choosing the new , should we still use the > T-1 ? > > (AFAIK) No. > replace_token is used when you want to replace a node that is dead. In > this case the dead node will be identified by its token. > > if so, would the duplicate token (same token but different ip) cause > problems? > > If the nodes are bootstrapping an error is raised. > Otherwise the token ownership is passed to the new node. > > Cheers > > ----------------- > Aaron Morton > Freelance Developer > @aaronmorton > http://www.thelastpickle.com > > On 15/08/2012, at 11:07 AM, Yang wrote: > > previously when a node dies, I remember the documents describes that it's > better to assign T-1 to the new node, > where T was the token of the dead node. > > > the new doc for 1.x here > > http://wiki.apache.org/cassandra/Operations#Replacing_a_Dead_Node > > > shows a new way to pass in cassandra.replace_token= > for the new node. > Using this method, when choosing the new , should we still use the > T-1 ? > > > Also in Priam code: > > https://github.com/Netflix/Priam/blob/master/priam/src/main/java/com/netflix/priam/identity/InstanceIdentity.java > > line 148, it does not seem that Priam does the "-1" thing, but assigns the > original token T to the new node. > if so, would the duplicate token (same token but different ip) cause > problems? > > > Thanks > Yang > > > --20cf3005149831200c04c746c7a0 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

thanks Aaron, it has been a while since i last checked the code,=A0 I= 9;ll read it to understand it more

On Aug 14, 2012 8:48 PM, "aaron morton"= ; <aaron@thelastpickle.com> wrote:

On 15/08/2012, at 11:07 AM, Yang <teddyyyy123@gmail.com> wrote:
previously when a node dies, I remembe= r the documents describes that it's better to assign T-1 to the new nod= e,
where T was the token of the dead node.


<= /div>
the new doc for 1.x here

http://wiki.apache.org/cassandra/Operat= ions#Replacing_a_Dead_Node


shows a ne= w way to =A0pass in=A0cassandra.replace_token=3D<Token> =A0
for the new node. =A0
Using this method, when choosing the n= ew <Token>, should we still use the T-1 ?

Also in Priam code:

line 148, it does not seem that Priam does the "-1= " thing, but assigns the original token T to the new node.
i= f so, would the duplicate token (same token but different ip) cause problem= s?


Thanks
Yang

--20cf3005149831200c04c746c7a0--