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 EEBCFDFF9 for ; Tue, 25 Sep 2012 10:23:03 +0000 (UTC) Received: (qmail 89348 invoked by uid 500); 25 Sep 2012 10:23:01 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 89285 invoked by uid 500); 25 Sep 2012 10:22:59 -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 89261 invoked by uid 99); 25 Sep 2012 10:22:59 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 25 Sep 2012 10:22:58 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of bigtvioletblue@yahoo.co.jp designates 114.111.99.93 as permitted sender) Received: from [114.111.99.93] (HELO web100118.mail.kks.yahoo.co.jp) (114.111.99.93) by apache.org (qpsmtpd/0.29) with SMTP; Tue, 25 Sep 2012 10:22:49 +0000 Received: (qmail 9217 invoked by uid 60001); 25 Sep 2012 10:22:23 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.co.jp; s=yj20110701; t=1348568543; bh=JMFjzr+b59uAJMXNgx5mEr/NIO2LqKBTJEHaHy/Vjgw=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type; b=gefxkyVN6M1XU49fyla2C5UM0do0AMAqV5QjZN6V8L/VfB5UAZLUMuCZbXcG3MgjJidcJp8pNQXQ9Wm4/ByVLKYWu1kJAoWVeLDNR6Ald9Za3EXjH/zLpAfINKwg/pmim0ldO5s3G/Qqm5TDlKefIsRFxmeFNOZBGK8C1sxyYRU= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=yj20110701; d=yahoo.co.jp; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type; b=QhIhl5YqkYgmNykGsYNGTiu3/SNI3EAsZlTNZ4iXEEO1DSVPLtG2wdpyAL92MUnYRulHif57SrRAwPC/9lUpPmpWtCiVdCcTE2QeNO/ES9MMjR31HgVRUw8b9j0J8VRz7UdsJP1DAvxi5R3zEWWV3VVwrn+LGKPvgQ5GD/plqOc=; Message-ID: <361031.6460.qm@web100118.mail.kks.yahoo.co.jp> X-YMail-OSG: eeqKJ4wVM1lIRj_0iS_sGNXklPtLbjAbHeLPPVqFi6akRQRyWUZZrcTJuCux__e6vFudsxpylWrQDAJF_DX0sVt2tl.BrIQ2avMUMyofrxiDBIy3vYQenwTn4ib.qI1I9KMJM8qhFGQ6cjkGUNeAtmIo0PFTbC1.urgauTYPwqVdxZTZqeF9EU1woe.0Y1q0QIJr.Z3FZ8IDykpMujgq4R0L6gALh7cOHvNlx9_a0n9cvLT4hp67INQ- Received: from [126.112.54.50] by web100118.mail.kks.yahoo.co.jp via HTTP; Tue, 25 Sep 2012 19:22:23 JST X-Mailer: YahooMailClassic/6.0.19_61 YahooMailWebService/0.8.111_27 Date: Tue, 25 Sep 2012 19:22:23 +0900 (JST) From: Satoshi Yamada Subject: a node stays in joining To: user@cassandra.apache.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-552282589-1348568543=:6460" --0-552282589-1348568543=:6460 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable hi, One node in my cluster stay in "joining". I found a jira about this, which = is fixed,but still sees the similar thing. This is a node I remove the toke= n first becauseit did not boot correctly and re-joined in the cluster witho= ut any pre-set token(shouldI set the previous token?). As you see below, the node(yyyy)'s state is Joining and Effective-Ownership= is 0.00 %for more than 10 hours. But the Load keeps on increasing. Also I noticed in the gossipinfo, the status of the node is BOOT while othe= r node is NORMAL. So, how can I get the status of the node to NORMAL? $ nodetool -h `hostname` ringAddress DC Rack St= atus Load State Load Effe...xxxx datacenter1 = rack1 Up Normal 122.41 MB 4.27 %.........y= yyy datacenter1 rack1 Up Joining 371.3= 3 MB 0.00 % $ nodetool -h `hostname` gossipinfo........yyyy/192.0.1.111 RELEASE=3DVER= SION:1.1.4 LOAD:3.89343423E8 STATUS:BOOT, 123123123....1312. SCHEMA:a= 442323-...... thanks,satoshi --0-552282589-1348568543=:6460 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
hi,

One node in my cluster= stay in "joining". I found a jira about this, which is fixed,
bu= t still sees the similar thing. This is a node I remove the token first bec= ause
it did not boot correctly and re-joined in the cluster witho= ut any pre-set token(should
I s= et the previous token?).

As you see below, = the node(yyyy)'s state is Joining and Effective-Ownership is 0.00 %
for more than 10 hours. But the Load keeps on increasing.

=
Also I noticed in the gossipinfo, the status of the node is BOOT= while other node is 
NORMAL.

So, h= ow can I get the status of the node to NORMAL?

$ n= odetool -h `hostname` ring
Address       &nbs= p;    DC       Rack  = ;          Status      = Load        State     Load =      Effe...
xxxx       datacenter1  = ;   rack1           Up       &= nbsp;     Normal &n= bsp; 122.41 MB        4.27 %
.....
....
= yyyy      datacenter1     rack1  =         Up            Jo= ining        371.33 MB    0.00 %
=


$ nodetool -h `hostname` gossipinfo
.= ...
....
yyyy/192.0.1.111
   RELEASE=3DVERSION:1.1.4
   LOAD:3.89343423E8
   STATUS:BOOT, = 123123123....1312.
 = ;  SCHEMA:a442323-......

thanks,
satoshi
--0-552282589-1348568543=:6460--