feat: Implement task expires #72
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When a task is configured with `expires` we should use that deadline instead of the consumer's configured default deadletter_at deadline. A tasks' expiration deadline can't be longer than the namespace's deadletter deadlines to prevent tasks from clogging up processing. Expiration deadlines start from when the task is added to kafka instead of the current time like a standard deadline. The reason for this is that tasks with expirations are often created by cron tasks, and the expiration time matches the tasks schedule. Refs #59
john-z-yang
approved these changes
Dec 6, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When a task is configured with
expireswe should use that deadline instead of the consumer's configured default deadletter_at deadline.A tasks' expiration deadline can't be longer than the namespace's deadletter deadlines to prevent tasks from clogging up processing.
Expiration deadlines start from when the task is added to kafka instead of the current time like a standard deadline. The reason for this is that tasks with expirations are often created by cron tasks, and the expiration time matches the tasks schedule.
Refs #59