> Indeed - today they would be lost. In that case should not we try for at-least-once. As in such a case nothing happened compared to other where some side affect got triggered. Probably by committing the Kafka offset post processing of the batch which got picked up?
Probably other similar services provide a at-least-once semantics. Chetan Mehrotra On Mon, May 14, 2018 at 10:50 PM, Rodric Rabbah <[email protected]> wrote: > Indeed - today they would be lost. > > It's also possible for the action to have run but no activation record is > created (invoker dies after executing the action). > > There are also sequences or conductor actions in the controller which are > not persisted while running and can be partially lost (ie no top level > activation but some or all of the sub-components may be observable). > > -r > > On Mon, May 14, 2018 at 1:15 PM, Chetan Mehrotra <[email protected]> > wrote: > >> Linked doc talks about 4 cases >> >> 1. success >> 2. application error >> 3. action developer error >> 4. whisk internal error >> >> From what I understand in each of above case an activation record >> would be created and client app/logic can know the outcome. So for >> these at least once the records were processed >> >> However what would happen to those activations which have been picked >> from Kafka queue but before processing them Invoker process got >> killed? Would they get lost? >> >> >> >> Chetan Mehrotra >> >> >> On Mon, May 14, 2018 at 4:59 PM, Rodric Rabbah <[email protected]> wrote: >> > At most once: https://github.com/apache/incubator-openwhisk/blob/ >> master/docs/reference.md#action-execution-guarantees >> > >> > >> > -r >> > >> >> On May 14, 2018, at 7:22 AM, Chetan Mehrotra <[email protected]> >> wrote: >> >> >> >> Do action invocations support "at least once" OR "at most once" >> >> semantics in response to an activation? >> >> >> >> Chetan Mehrotra >>
