Return-Path: Delivered-To: apmail-incubator-cassandra-user-archive@minotaur.apache.org Received: (qmail 65001 invoked from network); 23 Dec 2009 04:17:11 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 23 Dec 2009 04:17:11 -0000 Received: (qmail 82033 invoked by uid 500); 23 Dec 2009 04:17:10 -0000 Delivered-To: apmail-incubator-cassandra-user-archive@incubator.apache.org Received: (qmail 81976 invoked by uid 500); 23 Dec 2009 04:17:10 -0000 Mailing-List: contact cassandra-user-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cassandra-user@incubator.apache.org Delivered-To: mailing list cassandra-user@incubator.apache.org Received: (qmail 81967 invoked by uid 99); 23 Dec 2009 04:17:10 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 Dec 2009 04:17:10 +0000 X-ASF-Spam-Status: No, hits=-2.6 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of bburruss@real.com designates 207.188.23.7 as permitted sender) Received: from [207.188.23.7] (HELO cir-el.real.com) (207.188.23.7) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 Dec 2009 04:17:03 +0000 Received: from seacas02.corp.real.com ([::ffff:192.168.139.57]) (TLS: TLSv1/SSLv3,128bits,AES128-SHA) by cir-el.real.com with esmtp; Tue, 22 Dec 2009 20:16:43 -0800 id 001FC110.4B3199AB.00007F7A Received: from seambx.corp.real.com ([fe80::2d15:fda7:b3b8:e268]) by seacas02.corp.real.com ([::1]) with mapi; Tue, 22 Dec 2009 20:16:42 -0800 From: Brian Burruss To: "cassandra-user@incubator.apache.org" Date: Tue, 22 Dec 2009 20:16:42 -0800 Subject: Re: How know node is fully up? Thread-Topic: How know node is fully up? Thread-Index: AQHKgBCgZY+S8uTp/0ePJTffSFbslZFyDVSv Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 I never heard from anyone about this. I think it is important for bringing= nodes out of service during upgrades so no data loss occurs. Also when in= troducing a new node you need to know when it is fully populated. Tux! Brian Burruss 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 sim= ulated a crash. using tpstats i don't see any ROW-READ-STAGE completed, but lots of ROW-MUT= ATION-STAGE completed which seems to be correct for a node that is still sy= nc'ing with the cluster after being unavailable. .. but how do i know ;) thx!