[CASSSIDECAR-181] Ensure memory consistency from PeriodicTask executions and expose richer ScheduleDecision

• Type: Improvement
• Status: Review In Progress
• Priority: Major
• Resolution: Unresolved
• Component/s: Rest API
• Change Category: Semantic
• Complexity: Normal

Test and Documentation Plan

ci; unit

• Assignee: Yifan Cai
• Reporter: Yifan Cai

Reviewers

Francisco Guerrero

• Created: 21/Dec/24 19:34
• Updated: 3 days ago 20:43

Description

PeriodicTaskExecutor already ensures one active run of each periodic task at any time. However, the implementation cannot establish the happens-before ordering between 2 runs. Therefore, writes may not be visible to the next run. The patch changes the scheduling behavior in the executor to address the issue, so that the runs are properly ordered, serial as in a single thread.
The patch also addressed a todo left in the code to expose richer ScheduleDecision enum, instead of using boolean for shouldSkip.

Issue Links

• links to: GitHub Pull Request #167