Details
-
Bug
-
Status: Resolved
-
Low
-
Resolution: Fixed
-
None
-
None
-
Low
Description
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.