-
Notifications
You must be signed in to change notification settings - Fork 49
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
TriggerEngine: allow custom prefetch_count on trigger policies
Until now, a trigger policy used a consumer prefetch set by the `DATA_UPDATER_PLANT_AMQP_CONSUMER_PREFETCH_COUNT` env (as usual in Astarte). However, if consumer prefetch count > 1, ordered message delivery is not guaranteed, because messages might not be dequeued (thus processed) sequentially. However, this allows for higher throughput. Now, the `prefetch_count` policy field allows the user to set its the prefetch count. The default policy will still use the env var, so as not to break compatibility with previous Astarte versions. Signed-off-by: Arnaldo Cesco <[email protected]>
- Loading branch information
Showing
4 changed files
with
9 additions
and
6 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
This file contains 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