funky-eyes commented on issue #7840:
URL:
https://github.com/apache/incubator-seata/issues/7840#issuecomment-3635958042
根据SagaAnnotationActionInterceptorHandler的实现来看，目前使用了跟TCC一样的ActionInterceptorHandler，即在一阶段时会插入fencelog来保证防悬挂和空回滚，但是在SagaAnnotationResourceManager中并没有像TCCResourceManager那样调用
DefaultCommonFenceHandler.get()
.rollbackFence方法，导致saga注解模式的防悬挂和空回滚能力失效了，我认为是否像TCCResourceManager中那样处理rollback事件是否就可以达到空回滚和防悬挂的问题
According to the implementation of SagaAnnotationActionInterceptorHandler,
it currently uses the same ActionInterceptorHandler as TCC — that is, it
inserts a fence log in the first phase to ensure anti-suspension and empty
rollback protection. However, in SagaAnnotationResourceManager, unlike
TCCResourceManager, it does not call
DefaultCommonFenceHandler.get().rollbackFence when processing rollback events,
which causes the anti-suspension and empty rollback capabilities to fail (be
ineffective) in Saga annotation mode.
I think: if we handle the rollback event in SagaAnnotationResourceManager in
the same way as in TCCResourceManager, would that solve the empty rollback and
anti-suspension issues?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
