[ https://issues.apache.org/jira/browse/CASSANDRA-7012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14020615#comment-14020615 ]
Joaquin Casares commented on CASSANDRA-7012: -------------------------------------------- I've added this pull request to see if I can get around this via the java-driver: https://github.com/datastax/java-driver/pull/179 I've added this commit to do the same with the python-driver: https://github.com/datastax/python-driver/commit/a6d3c06a2aa98a5014e52bfff2384e25f56383cb I'll know more Monday when I check the newest Jenkins runs. > 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)