I plan to support the setting locally. Users can configure the maximum of retries for each transaction.
In addition, I still have a question about forwardPolicy. Should Saga execute Compensation when the number of transaction failures reaches the maximum of retries? For example, a Saga transaction includes three sub transaction A -> B -> C, and the maximum of retries is 10. When A succeeded and B failed 10 times, should A execute compensation or not? ------------------ ???????? ------------------ ??????: "Willem Jiang"<[email protected]>; ????????: 2018??10??18??(??????) ????10:42 ??????: "dev"<[email protected]>; ????: Re: [DISCUSS]The forwardPolicy of Saga should be able to configurethemaximum of retries I think we should support to apply the setting globally or locally. Willem Jiang Twitter: willemjiang Weibo: ????willem On Thu, Oct 18, 2018 at 8:27 PM Zheng Feng <[email protected]> wrote: > > Is it a global configration for all the transactions or it can be applied > for the specified one ? > > ???????????? <[email protected]> ??2018??10??16?????? ????5:17?????? > > > I create a new issue in JIRA. > > issue address: > > https://issues.apache.org/jira/browse/SCB-962 > > > > > > > > > > ------------------ ???????? ------------------ > > ??????: "Willem Jiang"<[email protected]>; > > ????????: 2018??10??16??(??????) ????4:29 > > ??????: "dev"<[email protected]>; > > > > ????: Re: [DISCUSS]The forwardPolicy of Saga should be able to configurethe > > maximum of retries > > > > > > > > Yeah, it makes sense to add the maximum number of forward retry. > > Could you fill a JIRA for it? > > It could be great if you can send a PR of this issue :) > > > > Willem Jiang > > > > Twitter: willemjiang > > Weibo: ????willem > > > > On Tue, Oct 16, 2018 at 4:22 PM ???????????? <[email protected]> wrote: > > > > > > Hi, all: > > > > > > > > > Currently, service comb saga would keep trying transaction part when > > using forwardPolicy. > > > The policy is sufficient for some situations, such as network > > fluctuations or service unavailability temporarily. > > > But for other situations like wrong address, wrong params or wrong SQL, > > it is possible to cause saga retry infinitely. > > > So, I recommend that Saga should be able to configure the maximum of > > retries for forwardPolicy. > > > When users configure the maximum of retries and transaction failed > > repeatedly, Saga should throw exception or do backward. > > > > > > > > > Best Wishes & Regards
