apache / apache/incubator-seata
How does Seata handle failed compensation transactions in SAGA mode?
Open
- Dominant language
- Java
- Stars
- 26k
- Forks
- 8.8k
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 4
Description
Suppose we have transaction T1->T2->T3, after T1 and T2 succeeded, T3 failed, then start compensation transactions C2 -> C1, if C2 fails, does the compensation process stop at C2 or does it record the failure and continue C1? how does Seata deal with such situations?
Contributor guide
Research direction
Start by reviewing Seata's SAGA compensation flow for T1→T2→T3 and the handling of a C2 failure. Confirm whether compensation stops or records the failure and continues with C1, then document the observed behavior and its implications.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- distributed-systems
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100