Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Mon, 9 Jun 2014 17:09:02 +0000 (UTC)
From: "Joaquin Casares (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12707306.1397001688984.94929.1402333742574@arcas>
In-Reply-To: <JIRA.12707306.1397001688984@arcas>
References: <JIRA.12707306.1397001688984@arcas>
Subject: [jira] [Commented] (CASSANDRA-7012) Expose node status through the
 system tables, especially after the native protocol is active
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CASSANDRA-7012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14025369#comment-14025369 ] 

Joaquin Casares commented on CASSANDRA-7012:
--------------------------------------------

Now waiting on https://github.com/pcmanus/ccm/pull/125 since the last pull request was only at the node level. This new pull request adds cluster-level support for those wait commands.

> Expose node status through the system tables, especially after the native protocol is active
> --------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-7012
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7012
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: API
>            Reporter: Joaquin Casares
>            Assignee: Tyler Hobbs
>              Labels: datastax_qa
>
> Java-Driver's note on the issue: https://github.com/datastax/java-driver/blob/2.1/driver-core/src/main/java/com/datastax/driver/core/Cluster.java#L1087
> What the tests for the drivers (Java, Python, C#, etc..) see is a need for sleeps to cover the race conditions between when isUp() returns true and the nodes are actually ready to be accessed.
> Could we instead, at the very end of the startup process when the native protocol is up and active, have the system tables be written to denote that the node is now UP and active?
> If writing to the system tables is not the best idea, could we figure out another solution to get rid of this race condition, thereby simplifying the testing of the drivers and removing test cases riddled with sleeps of up to 40 seconds?


--
This message was sent by Atlassian JIRA
(v6.2#6252)