[ https://issues.apache.org/jira/browse/CASSANDRA-9329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14533614#comment-14533614 ]
Aaron Whiteside edited comment on CASSANDRA-9329 at 5/7/15 11:43 PM: --------------------------------------------------------------------- Can we at least get something into the next 2.x release? Perhaps if cas_contention_timeout_in_ms is set to 0, then we never sleep and only try the condition once? The configurable alg and timeout can come later. was (Author: aaronjwhiteside): Can we at least get something into the next 2.x release? Perhaps if cas_contention_timeout_in_ms is set to 0, then we never sleep and only try the condition once? > Make CAS retry logic configurable > --------------------------------- > > Key: CASSANDRA-9329 > URL: https://issues.apache.org/jira/browse/CASSANDRA-9329 > Project: Cassandra > Issue Type: Improvement > Components: Core > Reporter: Aaron Whiteside > Fix For: 3.x > > > Make CAS retry logic configurable: > One should be able to disable the internal CAS retry loop (when the condition > is not met) and let the client choose how to do retries (so the client does > not have to incur the server side random sleep of up to 100ms). Basically let > the client handle all CAS retries in a manor it sees fit. > Secondly the hardcoded sleep up to 100ms that happens when cassandra fails to > meet the CAS condition should be configurable. > - The max duration should be configurable > - The algorithm used to choose the duration should be configurable (Random, > Exponential, etc). -- This message was sent by Atlassian JIRA (v6.3.4#6332)