cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tyler Hobbs (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (CASSANDRA-7012) Expose node status through the system tables, especially after the native protocol is active
Date Wed, 09 Apr 2014 17:50:16 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-7012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Tyler Hobbs reassigned CASSANDRA-7012:
--------------------------------------

    Assignee: Tyler Hobbs

> 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)

Mime
View raw message