Mailing-List: contact cassandra-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cassandra-user@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of bburruss@real.com designates
 207.188.23.7 as permitted sender)
From: Brian Burruss <bburruss@real.com>
To: 
  "cassandra-user@incubator.apache.org" <cassandra-user@incubator.apache.org>
Date: Wed, 23 Dec 2009 08:28:41 -0800
Subject: RE: How know node is fully up?
Thread-Topic: How know node is fully up?
Thread-Index: AcqDi6Fd44lECAjmTda1HcmTpaU7GwAYVuyx
Message-ID: <766B5A29D28DA442AB229AAEE2AFC44507D7B9150C@SEAMBX.corp.real.com>
References: 
 <diqn8t0g5gjdxoxkq1o11jmf.1261541663496@email.android.com>,<e06563880912222050i6dd4b04ag9a586498dca2131a@mail.gmail.com>
In-Reply-To: <e06563880912222050i6dd4b04ag9a586498dca2131a@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

when i see this message it seems like it is still not responding to read re=
quests, so IMO it isn't fully up and operational.  i assume it is still "ha=
nding off" or some other sync operation.

i think a JMX paramater should be exposed that contains the "state" of a no=
de.

________________________________________
From: Jonathan Ellis [jbellis@gmail.com]
Sent: Tuesday, December 22, 2009 8:50 PM
To: cassandra-user@incubator.apache.org
Subject: Re: How know node is fully up?

It's up when it logs "Cassandra starting up..." and starts listening
for thrift connections

On Tue, Dec 22, 2009 at 10:16 PM, Brian Burruss <bburruss@real.com> wrote:
> I never heard from anyone about this.  I think it is important for bringi=
ng nodes out of service during upgrades so no data loss occurs.  Also when =
introducing a new node you need to know when it is fully populated.
>
> Tux!
>
> Brian Burruss <bburruss@real.com> wrote:
>
>
> How can i tell that a node is completely up and taking reads and writes?
>
> - at startup?
> - after new bootstrap?
> - after a node has been unavailable for some time and rejoins the cluster=
?
>
> i see the "INFO [main] [CassandraDaemon.java:141] Cassandra starting up..=
." message in the log, but it seems to have happened way too fast after i s=
imulated a crash.
>
> using tpstats i don't see any ROW-READ-STAGE completed, but lots of ROW-M=
UTATION-STAGE completed which seems to be correct for a node that is still =
sync'ing with the cluster after being unavailable.
>
> .. but how do i know ;)
>
> thx!
>