Looking forward to call compensation functions immediately in case of one aborted event.

[jiuang]

So far, if Saga encountered an aborted event, then it could not execute compensation functions immediately yet. Instead, the Alpha EventScanner tool would call compensation methods within 500ms.

As we all know, 500ms is a long time in terms of computer. That will lead to a lot of wrong data probably. Hope to reduce the frequencies on errors, even though we could not solve it completely at present.

Please point them out when I make mistakes. Thank you!

[WillemJiang]

Using the EventScanner is a challenge for us to handle the timeout event, we will do some modification here. Since Saga only provides the eventual consistent, we cannot guarantee that data is always right consistent here event we reduce the time to 1ms.

[jiuang]

Yeah, I understood. I just hope that we can make it be better. That's all.

[WillemJiang]

@Gannalyo Can you close this issue if the answer address your question?

[jiuang]

Hi Jiang! I have received your email. I intend to notice that issue at next week. And I will send message to your email later. Thanks a lot.

At 2018-08-08 16:11:44, "Willem Jiang" [email protected] wrote:

@Gannalyo Can you close this issue if the answer address your question?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[WillemJiang]

Once the Alpha got the abort message , it knows about the transaction is failed and it can call the compensation method directly , the event scanner is just for the timeout event. I just fill a JIRA SCB-835 for it.