cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksey Yeschenko (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-14338) Fix scheduling of speculative retry threshold recalculation
Date Fri, 23 Mar 2018 14:00:00 GMT


Aleksey Yeschenko updated CASSANDRA-14338:
    Resolution: Fixed
        Status: Resolved  (was: Ready to Commit)

> Fix scheduling of speculative retry threshold recalculation
> -----------------------------------------------------------
>                 Key: CASSANDRA-14338
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Aleksey Yeschenko
>            Assignee: Aleksey Yeschenko
>            Priority: Major
>             Fix For: 4.0
> Realized after committing CASSANDRA-14293 that it's slightly broken: when updating from
a static to a dynamic speculative retry policy, the refresher will never be scheduled.
> Also realised that the whole thing is a bit dumb. We don't need a latency calculator
runnable per {{ColumnFamilyStore}}, we should have one per node, that does in batch refresh
thresholds for every table. It's one fewer thing to manage, and allows to get rid of {{isDynamic()}}
method in {{SpeculativeRetryPolicy}}, which I thought was clever at the time.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message