You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "David Capwell (Jira)" <ji...@apache.org> on 2023/05/09 19:56:00 UTC
[jira] [Updated] (CASSANDRA-18510) CEP 15: (Accord) push waiting for epoch into CommandStore rather than require every command to think about the edge case when the epoch isn't ready
[ https://issues.apache.org/jira/browse/CASSANDRA-18510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Capwell updated CASSANDRA-18510:
--------------------------------------
Change Category: Code Clarity
Complexity: Normal
Fix Version/s: 5.x
Status: Open (was: Triage Needed)
I think this is low hanging fruit, but there maybe a dragon I didn't consider/know about, so left this as Normal
> CEP 15: (Accord) push waiting for epoch into CommandStore rather than require every command to think about the edge case when the epoch isn't ready
> ---------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-18510
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18510
> Project: Cassandra
> Issue Type: Improvement
> Components: Accord
> Reporter: David Capwell
> Priority: Normal
> Fix For: 5.x
>
>
> We have a common pattern of scheduling work on a CommandStore, but this work has to double check the epoch exists, if not it has to wait on the fetch and reschedule again… this pattern could likely be pushed to CommandStore if the PreLoadContext includes the epochs required (just like we do for commands).
> For things outside of CommandStores, they would have to maintain their current logic, the scope of this work is just tasks that run on CommandStores.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org