[
https://issues.apache.org/jira/browse/CASSANDRA-7955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14137362#comment-14137362
]
Brandon Williams commented on CASSANDRA-7955:
---------------------------------------------
We could also just automatically bump ring delay up if the write timeout is
greater.
> Range movements can violate consistency if RING_DELAY <=
> write_request_timeout_in_ms
> ------------------------------------------------------------------------------------
>
> Key: CASSANDRA-7955
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7955
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Benedict
> Priority: Minor
>
> Cassandra should probably refuse to start if RING_DELAY is too close to (or
> below) write_request_timeout_ms, because we depend on this for
> correctness/consistency during range movements
> We should probably also consider throwing a WriteTimeoutException _even if we
> don't get interrupted by the timeout, since there are reasons due to
> scheduling or system overload this could not happen (though it is unlikely to
> be significant enough to have an impact, it's better safe than sorry)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
