-
-
Notifications
You must be signed in to change notification settings - Fork 102
Open
Labels
A-routingArea: Message routing internalsArea: Message routing internalsC-feature-compatCategory: Feature CompatibilityCategory: Feature CompatibilityC-feature-requestCategory: Feature RequestCategory: Feature Request
Description
Is your feature request related to a problem? Please describe.
For the autoscaling feature (PR #202) would be great to have an ack mechanism for the processed message, that could help eliminate an issues around dropping actors that took the message but the executed future in the pending state.
Describe the solution you'd like
For any message, whatever its type and method that was used for getting a message from the queue, we always have to acknowledge (let's call just it as the ack call) the processed message or to skip it.
Benefits of the usage:
- Actors can retrieve messages with the
Exactly-Onceguarantees - More reliable mechanism for tracking the current state of the actors and systems based on Bastion codebase
Possible ways to implement it:
- Extend the implementation for the SignedMessage: add the
ack/acknowledgemethod for confirming that the message was processed and can be removed from the mailbox. - Add the
message_processedmethod for theBastionContextstruct, that can be called inside of the actor's future
Describe alternatives you've considered
N/A
Metadata
Metadata
Assignees
Labels
A-routingArea: Message routing internalsArea: Message routing internalsC-feature-compatCategory: Feature CompatibilityCategory: Feature CompatibilityC-feature-requestCategory: Feature RequestCategory: Feature Request