Closed fernando-a-marins closed 1 year ago
In a rebalance scenario, the triggers accumulate jobs and then fire several jobs one following the other.
In this case, we should only fire one job for each cron expression hit.
Proposed Solution:
Use on triggers configuration the policy WithMisfireHandlingInstructionDoNothing.
WithMisfireHandlingInstructionDoNothing
Have several instances running the kafka flow retry extension Provoke several rebalances Have a job with considerable short cron expression
In a rebalance scenario, the triggers should not accumulate jobs, just fire the job when the corn expression is hit again.
2.1.0
Addressed in the release: https://github.com/Farfetch/kafkaflow-retry-extensions/releases/tag/2.1.1
Prerequisites
Description
In a rebalance scenario, the triggers accumulate jobs and then fire several jobs one following the other.
In this case, we should only fire one job for each cron expression hit.
Proposed Solution:
Use on triggers configuration the policy
WithMisfireHandlingInstructionDoNothing
.Steps to reproduce
Have several instances running the kafka flow retry extension Provoke several rebalances Have a job with considerable short cron expression
Expected behavior
In a rebalance scenario, the triggers should not accumulate jobs, just fire the job when the corn expression is hit again.
Actual behavior
In a rebalance scenario, the triggers accumulate jobs and then fire several jobs one following the other.
KafkaFlow Retry Extensions version
2.1.0