[
https://issues.apache.org/jira/browse/CASSANDRA-19454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Caleb Rackliffe updated CASSANDRA-19454:
----------------------------------------
Bug Category: Parent values: Availability(12983)
Complexity: Low Hanging Fruit
Component/s: Messaging/Client
Discovered By: Code Inspection
Fix Version/s: 5.0.x
5.x
Severity: Low
Status: Open (was: Triage Needed)
> Revert switch to approximate time in Dispatcher to avoid mixing with
> nanoTime() in downstream timeout calculations
> ------------------------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-19454
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19454
> Project: Cassandra
> Issue Type: Bug
> Components: Messaging/Client
> Reporter: Caleb Rackliffe
> Assignee: Caleb Rackliffe
> Priority: Normal
> Fix For: 5.0.x, 5.x
>
>
> CASSANDRA-15241 changed {{Dispatcher}} to use the {{approxTime}}
> implementation of {{MonotonicClock}} rather than {{nanoTime()}}, but clock
> drift between the two, can potentially cause queries to time out more
> quickly. We should be able to revert the {{Dispatcher}} to use {{nanoTime()}}
> again and similarly change {{QueriesTable} to {{nanoTime()}} as well for
> consistency.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
