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 492D21891A for ; Tue, 12 May 2015 19:11:19 +0000 (UTC) Received: (qmail 96404 invoked by uid 500); 12 May 2015 19:11:16 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 96367 invoked by uid 500); 12 May 2015 19:11:16 -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 96356 invoked by uid 99); 12 May 2015 19:11:16 -0000 Received: from Unknown (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 May 2015 19:11:16 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 198ED18294F for ; Tue, 12 May 2015 19:11:16 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.9 X-Spam-Level: ** X-Spam-Status: No, score=2.9 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-eu-west.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id o12noCS-jkMo for ; Tue, 12 May 2015 19:11:01 +0000 (UTC) Received: from mail-yk0-f171.google.com (mail-yk0-f171.google.com [209.85.160.171]) by mx1-eu-west.apache.org (ASF Mail Server at mx1-eu-west.apache.org) with ESMTPS id 45C8724CE5 for ; Tue, 12 May 2015 19:11:00 +0000 (UTC) Received: by ykeo186 with SMTP id o186so6614165yke.0 for ; Tue, 12 May 2015 12:10:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=CAp2YYrVVpJYYoU3Fenj1fnObcrB5Tf/ezwxHqiCDfk=; b=crGK03NQjs+28uenaZAVJ5supsO4znsXLBV03fFUDqwAkNN4QwoStjCBW5Vuq3XY4r DRZCsuQyM+uv3JGYLJ6YjuJ0GjE9/jLu18tO6vJJ+3WL9r2fkKJnTc4rogu9OC5Ok1q1 wq5CmigVlK6NIUWBF5Zg4RVsXNgEqrEfetYoSanY2KUs1ZBoe2+QX+6j7u/E5SDp2Z8e V721xlsIQlEcASEUzljPW9nli37to7QcLxEsAkxdUO/zxwMduOPUyVsQNNKIUkwxmMoh SSuC5dzyWAAR6j/Iuz6g0ZEuDz8fWNjpWN1shG3j/OtptTvdMJ28wUHBCslZy12GvTZf OYIQ== X-Received: by 10.236.231.146 with SMTP id l18mr16901377yhq.122.1431457853250; Tue, 12 May 2015 12:10:53 -0700 (PDT) MIME-Version: 1.0 Received: by 10.129.145.134 with HTTP; Tue, 12 May 2015 12:10:32 -0700 (PDT) In-Reply-To: References: From: Analia Lorenzatto Date: Tue, 12 May 2015 16:10:32 -0300 Message-ID: Subject: Re: Unexpected behavior after adding successffully a new node To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=047d7b5d2d32daa2900515e74089 --047d7b5d2d32daa2900515e74089 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Just in case I want to clarify that after bootstrapping the third node, it got data and seemed to be working fine. But it was the last night when the cluster started behaving in a weird way. The last node (successfully added last week) were being reported up and down all the time. After restarting cassandra service, the node got empty but reported as Up and Normal. Also, the amount of data reported by nodetool on the other nodes is much more than the amount already used in the device, is that normal? root@10.0.0.a:~# df -h /mnt Filesystem Size Used Avail Use% Mounted on /dev/xvdb1 745G 163G 583G 22% /mnt/cassandra root@:10.0.0.b~$ df -h /mnt Filesystem Size Used Avail Use% Mounted on /dev/xvdb1 745G 196G 550G 27% /mnt/cassandra # nodetool status Datacenter: us-east =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Status=3DUp/Down |/ State=3DNormal/Leaving/Joining/Moving -- Address Load Tokens Owns (effective) Host ID Rack UN 10.0.0.a 391.34 GB 256 66.7% eed9e9f5-f279-4b2f-b521-c056cbf65b52 1c UN 10.0.0.b 383.38 GB 256 68.3% 19492c26-4458-4a0b-af04-72e0aab6598e 1c Thanks in advance! On Tue, May 12, 2015 at 2:35 PM, Robert Coli wrote: > On Tue, May 12, 2015 at 9:59 AM, arun sirimalla > wrote: > >> Try running repair on node 3. >> > > Mostly disagree. If a node is empty after a bootstrap, remove it and > re-bootstrap it. > > =3DRob > > --=20 Saludos / Regards. Anal=C3=ADa Lorenzatto. =E2=80=9CIt's possible to commit no errors and still lose. That is not weak= ness. That is life". By Captain Jean-Luc Picard. --047d7b5d2d32daa2900515e74089 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Just in case I want to clarify that after bootstrapping th= e third node, it got data and seemed to be working fine.=C2=A0 But it was t= he last night when =C2=A0the cluster started behaving in a weird way.=C2=A0= The last node (successfully added last week) were being reported up and do= wn all the time. After restarting cassandra service, the node got empty but= reported as Up and Normal.

Also, the amount of data rep= orted by nodetool on the other nodes is much more than the amount already u= sed in the device, is that normal?

root@10.0.= 0.a:~# df -h /mnt
Filesystem =C2=A0 =C2=A0 =C2=A0Size =C2=A0Used = Avail Use% Mounted on
/dev/xvdb1 =C2=A0 =C2=A0 =C2=A0745G =C2=A01= 63G =C2=A0583G =C2=A022% /mnt/cassandra

root@:10.0.0.b~$ df -h /mnt
Filesystem =C2=A0 =C2=A0 =C2=A0Size = =C2=A0Used Avail Use% Mounted on
/dev/xvdb1 =C2=A0 =C2=A0 =C2=A07= 45G =C2=A0196G =C2=A0550G =C2=A027% /mnt/cassandra


# nodetool status
Datacenter: us-east<= /div>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Status=3DUp/Down
|/ State=3DNormal/Leaving/Joining/Moving
-- =C2=A0Address =C2=A0 =C2=A0 Load =C2=A0 =C2=A0 =C2=A0 Tokens =C2= =A0Owns (effective) =C2=A0Host ID =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0= =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Rack
<= div>UN =C2=A010.0.0.a =C2=A0391.34 GB =C2=A0256 =C2=A0 =C2=A0 66.7% =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 eed9e9f5-f279-4b2f-b521-c056cbf65b52 =C2= =A01c
UN =C2=A010.0.0.b =C2=A0383.38 GB =C2=A0256 =C2=A0 =C2=A0 6= 8.3% =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 19492c26-4458-4a0b-af04-72e0= aab6598e =C2=A01c

Thanks in advance!




On Tue, May 12, 2015 at 2:35 PM, Robert= Coli <rcoli@eventbrite.com> wrote:
On Tue, May 12, 2015 at 9:59 AM, arun sirimalla = <arunsirik@gmail.com> wrote:
Try running repair on node 3.

Mostly disagree. If a node is empty after = a bootstrap, remove it and re-bootstrap it.

=3DRob=
=C2=A0



--
Saludos / Regards.

Anal=C3=ADa Lorenzatto.

=E2=80=9CIt's possible to commit no err= ors and still lose. That is not weakness.=C2=A0 That is life".=C2=A0 B= y Captain Jean-Luc Picard.
--047d7b5d2d32daa2900515e74089--