[jira] [Assigned] (CASSANDRA-6177) remove all sleeps in the dtests
[ https://issues.apache.org/jira/browse/CASSANDRA-6177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philip Thompson reassigned CASSANDRA-6177: -- Assignee: Philip Thompson remove all sleeps in the dtests --- Key: CASSANDRA-6177 URL: https://issues.apache.org/jira/browse/CASSANDRA-6177 Project: Cassandra Issue Type: Test Reporter: Brandon Williams Assignee: Philip Thompson The dtests use a ton of sleep calls for various things, most of which is guessing if Cassandra has finished doing something or not. Guessing is problematic and shouldn't be necessary -- a prime example of this is creating a ks or cf. When done over cql, we sleep and hope it's done propagating, but when done over thrift we actually check for schema agreement. We should be able to eliminate the sleeps and reliably detect when it's time for the next step programmatically. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (CASSANDRA-6177) remove all sleeps in the dtests
[ https://issues.apache.org/jira/browse/CASSANDRA-6177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryan McGuire reassigned CASSANDRA-6177: --- Assignee: Daniel Meyer (was: Ryan McGuire) remove all sleeps in the dtests --- Key: CASSANDRA-6177 URL: https://issues.apache.org/jira/browse/CASSANDRA-6177 Project: Cassandra Issue Type: Test Reporter: Brandon Williams Assignee: Daniel Meyer The dtests use a ton of sleep calls for various things, most of which is guessing if Cassandra has finished doing something or not. Guessing is problematic and shouldn't be necessary -- a prime example of this is creating a ks or cf. When done over cql, we sleep and hope it's done propagating, but when done over thrift we actually check for schema agreement. We should be able to eliminate the sleeps and reliably detect when it's time for the next step programmatically. -- This message was sent by Atlassian JIRA (v6.1#6144)
