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

Russell Alexander Spitzer reassigned CASSANDRA-7821:
----------------------------------------------------

    Assignee: Russell Alexander Spitzer

> Add Optional Backoff on Retry to Cassandra Stress
> -------------------------------------------------
>
>                 Key: CASSANDRA-7821
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7821
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Russell Alexander Spitzer
>            Assignee: Russell Alexander Spitzer
>
> Currently when stress is running against a cluster which occasionally has 
> nodes marked as down, it will almost immediately stop. This occurs because 
> the retry loop can execute extremely quickly if each execution terminates 
> with a {{com.datastax.driver.core.exceptions.NoHostAvailableException}} or 
> {{com.datastax.driver.core.exceptions.UnavailableException}}. 
> In case of these  exceptions is will most likely be unable to succeed if the 
> retries are performed as fast as possible. To get around this, we could add 
> an optional delay on retries giving the cluster time to recover rather than 
> terminating the stress run. 
> We could make this configurable, with options such as:
> * Constant # Delays the same amount after each retry
> * Linear # Backoff a set amount * the trial number
> * Exponential # Backoff set amount * 2 ^ trial number
> This may also require adjusting the "thread is stuck check" to make sure that 
> the max retry timeout will not cause the thread to be terminated early.



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

Reply via email to