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 2609110F18 for ; Mon, 1 Dec 2014 07:00:54 +0000 (UTC) Received: (qmail 14936 invoked by uid 500); 1 Dec 2014 07:00:50 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 14891 invoked by uid 500); 1 Dec 2014 07:00:50 -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 14881 invoked by uid 99); 1 Dec 2014 07:00:50 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 01 Dec 2014 07:00:50 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jens.rantil@tink.se designates 209.85.192.43 as permitted sender) Received: from [209.85.192.43] (HELO mail-qg0-f43.google.com) (209.85.192.43) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 01 Dec 2014 07:00:45 +0000 Received: by mail-qg0-f43.google.com with SMTP id q108so7040878qgd.2 for ; Sun, 30 Nov 2014 23:00:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tink.se; s=tink; h=date:mime-version:message-id:in-reply-to:references:from:to:subject :content-type; bh=iNnCqptN8jsU5UiguH66K3LBmORplBl78HIsNgPlvnY=; b=EYySFwYcwE1vzMuQSrmHNVPZ2Oxm5xdHkfV2Ka4QLox40duyuhooU1YH0eZGrpf1RJ dInCiuhX/JGIZLjEJe6CMxtHauJrKrhmu/pXppS6fAFXm2mn4Flo48yamjiLJr/KPQZi A+r7NNuTSXQz1/hodJyHwC5vnUz1LcmwqTXn8= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:mime-version:message-id:in-reply-to :references:from:to:subject:content-type; bh=iNnCqptN8jsU5UiguH66K3LBmORplBl78HIsNgPlvnY=; b=GxH2eS5I9jnyuWBNHx1iP1+b68jpQrAzYFwNdI98nMcBMDXG5Ljlf7h5qt4Vo7Eqnr 8le5eVy4CE+e64ZBHw3ZinZ3u1fEGIByA7369AGPTjQrT9qeAElBDILCaVmfgk03Mpa6 xtuUR28fMppz1enu4+RMe2HzZEFKVOP23cf1vOWK9FI3c7eLgNQdwFNkwHMgXd1hHyPt P/WM7IOygQ0kIjDJM7hrUqJPzl/MdoD7HsMgdoFXBhbqJY1fDGVbnJxHnbmZ8lKkOQl2 Ml37GuoQdq7N9SAzDql10UZlJ/RZE+ypke3POx6Z11HcwvYCnYbR46BgUktMem8oYEeK 57pA== X-Gm-Message-State: ALoCoQkUZ/uO6m6+yAhFCMa8b5rxo9h2dh0kI9qjeew11FG2iXpQ/qrXDjNk0WZTVSToHo4vSVDx X-Received: by 10.224.114.81 with SMTP id d17mr65101793qaq.27.1417417224022; Sun, 30 Nov 2014 23:00:24 -0800 (PST) Received: from hedwig-22.prd.orcali.com (ec2-54-85-253-234.compute-1.amazonaws.com. [54.85.253.234]) by mx.google.com with ESMTPSA id k66sm1944248qgd.21.2014.11.30.23.00.23 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 30 Nov 2014 23:00:23 -0800 (PST) Date: Sun, 30 Nov 2014 23:00:23 -0800 (PST) X-Google-Original-Date: Mon, 01 Dec 2014 07:00:23 GMT MIME-Version: 1.0 X-Mailer: Nodemailer (0.5.0; +http://www.nodemailer.com/) Message-Id: <1417417223179.5b852527@Nodemailer> In-Reply-To: References: X-Orchestra-Oid: BCECC19B-5DDB-4AE0-AC7F-487B842A08B2 X-Orchestra-Sig: 53d36df3e512d8741b50d8117173047e4c5a9c19 X-Orchestra-Thrid: T80A81801-1388-4D36-90EB-0696711C54C9_1486266867135972964 X-Orchestra-Thrid-Sig: f22cecca2b5afec185dbbbd6a92e445385add53b X-Orchestra-Account: 33c0d3b54e08b1bad1e6ae0e6593c65bf303e389 From: "Jens Rantil" To: user@cassandra.apache.org Subject: Re: Cassandra add a node and remove a node Content-Type: multipart/alternative; boundary="----Nodemailer-0.5.0-?=_1-1417417223503" X-Virus-Checked: Checked by ClamAV on apache.org ------Nodemailer-0.5.0-?=_1-1417417223503 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi Neha, Generally best practice is to add the new node before removing the old one.= This is especially important if the cluster=E2=80=99s resources (such as = available disk space) are low. Also, adding a node usually asserts that the= node is functioning correctly (check logs) before decommisioning the old = node. See [1]. [1] http://www.datastax.com/documentation/cassandra/2.= 0/cassandra/operations/ops=5Freplace=5Flive=5Fnode.html Cheers, Jens =E2=80=94=E2=80=94=E2=80=94 Jens Rantil Backend engineer Tink AB Email:=C2=A0jens.rantil@tink.se Phone: +46 708 84 18 32 Web:=C2=A0www.tink.se Facebook=C2=A0Linkedin=C2=A0Twitter On Mon, Dec 1, 2014 at 7:15 AM, Neha Trivedi wrote: > Hi, > I need to Add new Node and remove existing node. > Should I first remove the node and then add a new node or Add new node = and > then remove existing node. > Which practice is better and things I need to take care=3F > regards > Neha ------Nodemailer-0.5.0-?=_1-1417417223503 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
Hi Neha,

Generally best practice is to add the new node before removing the old= one. This is especially important if the cluster=E2=80=99s resources (such= as available disk space) are low. Also, adding a node usually asserts that= the node is functioning correctly (check logs) before decommisioning the = old node. See [1].

[1] http://www.datastax.com/documentation/cassandra/2.= 0/cassandra/operations/ops=5Freplace=5Flive=5Fnode.html

Cheers,
Jens


=E2=80=94=E2=80=94=E2=80=94 Jens Rantil Backend engineer Tink AB Email:=C2=A0jens.rantil@tink.se Phone: +46 708 84 18 32 Web:=C2=A0www.tink.se Facebook=C2=A0Linkedin=C2=A0Twitter


On Mon, Dec 1, 2014 at 7:15 AM,= Neha Trivedi <nehajtrivedi@gmail.com> = wrote:

Hi,
I need to Add new Node and remove existing node. =

Should I first remove the node and then add a new node or Add new node= and then remove existing node.
Which practice is better and things I need to take = care=3F

regards
Neha

------Nodemailer-0.5.0-?=_1-1417417223503--