Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
MIME-Version: 1.0
Sender: scode@scode.org
In-Reply-To: 
 <CANN9sNp-7ndC4EufFBriMJZW5FuUDz0MXDq25W3OxTsSF6NhvQ@mail.gmail.com>
References: 
 <CANN9sNpwiw=APFmzQOjSMgSZtGXJ-w71npy=_ny4+rOw-vn55Q@mail.gmail.com>
	<CAO5xsd24a5gJ=8sJTStqvcvr7dozV3RtEEMNJtP4Z_X4RAxsbg@mail.gmail.com>
	<CANN9sNp-7ndC4EufFBriMJZW5FuUDz0MXDq25W3OxTsSF6NhvQ@mail.gmail.com>
Date: Fri, 19 Aug 2011 20:43:37 +0200
Message-ID: 
 <CAO5xsd3Gy0X0DwZpAd-pRFR4nq83c_88GHNcyB93zeFxh=5reA@mail.gmail.com>
Subject: Re: Urgent:!! Re: Need to maintenance on a cassandra node, are there
 problems with this process
From: Peter Schuller <peter.schuller@infidyne.com>
To: user@cassandra.apache.org
Content-Type: text/plain; charset=UTF-8

> I am running read/write at quorum. At this point I have turned off my
> clients from talking to this node. So if that is the case I can potentially
> just nodetool repair (without changing IP). But would it be better if I

No, other nodes in the cluster will still be sending reads to the node.

> copied over the data/mykeyspace from another replica and then run repair?

The key thing is that unless you're willing to accept the node serving
reads with incorrect data, you need the node to initiate a normal
bootstrapping process whereby it starts taking writes as it is
bootstrapping, but won't take reads until it's done. This requires
that other nodes know that it is joining the ring; if you just pop it
back in they won't know that.

-- 
/ Peter Schuller (@scode on twitter)