[
https://issues.apache.org/jira/browse/CASSANDRA-5014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13694082#comment-13694082
]
Sylvain Lebresne commented on CASSANDRA-5014:
---------------------------------------------
As far as 2.0 is concerned, I'd vote to sticking to retry timeouts. For request
timeouts, it's not that I'm opposed to making them more precise in practice,
but currently we don't even really respect what we pretend those do (typically,
read_request_timeout_in_ms is said to be "How long the coordinator should wait
for read operations to complete", but in theory a coordinator may wait a lot
more than that if there is some repair results to wait on and some short-read
retry).
Now if we do CASSANDRA-5239 (which I hope we will), it'll change the meaning of
those timeout to be actual user query timeouts. It felt that this will be a
good time then to switch the unit for them, but doing it now will just probably
force upgrading people to change twice their yaml (for 2.0 and then for 2.1)
for no big value imo.
There's also the fact that I'd really want to get 2.0 beta1 out of the door so
if we can restrict the scope of this ticket a bit, I like it too.
> Convert timeout from milli second to micro second.
> --------------------------------------------------
>
> Key: CASSANDRA-5014
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5014
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Affects Versions: 2.0 beta 1
> Reporter: Vijay
> Assignee: Vijay
> Priority: Trivial
> Fix For: 2.0 beta 1
>
> Attachments: 0001-CASSANDRA-5014.patch
>
>
> Convert all the timeouts to microseconds.
> Jonathan's comment from CASSANDRA-4705
> {quote}
> millis may be too coarse a grain here, especially for Custom settings.
> Currently an in-memory read will typically be under 2ms and it's quite
> possible we can get that down to 1 if we can purge some of the latency
> between stages. Might as well use micros since Timer gives it to us for free
> {quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
