You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Aleksey Yeschenko (JIRA)" <ji...@apache.org> on 2018/03/23 13:11:00 UTC
[jira] [Updated] (CASSANDRA-14338) Fix scheduling of speculative
retry threshold recalculation
[ https://issues.apache.org/jira/browse/CASSANDRA-14338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aleksey Yeschenko updated CASSANDRA-14338:
------------------------------------------
Reviewer: Sam Tunnicliffe
Fix Version/s: (was: 4.x)
4.0
Status: Patch Available (was: Open)
> Fix scheduling of speculative retry threshold recalculation
> -----------------------------------------------------------
>
> Key: CASSANDRA-14338
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14338
> 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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org