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
