提一个边界性的问题
Open
- Dominant language
- Java
- Stars
- 1.9k
- Forks
- 644
- PR merge metrics
- No merged PRs in 30d
Description
先赞叹一下,作者真大牛。
A调用了S1,S2,S3服务,运行正常进入提交事务的过程。S1提交正常,S2提交正常。**但是提交S3的时候,可S3的网络出现问题,或者是S3对应的DB3数据库宕机**。
这个时候会陷入这样的境地,那就是S1,和S2的事务已经提交,没法回滚,也没有办法让S3提交。这个问题要怎么处理?
还有,本地服务的补偿,是一个什么样的机制呢?因为并没有看到关于补偿的介绍
Contributor guide
No contributing guide indexed for this repository
Research direction
No files, tests, or entry points are named in the issue. Start by reading the project documentation and transaction-handling entry points to locate the behavior for a failed S3 or DB3 commit. Done means documenting the failure case and the local compensation mechanism clearly enough to explain what happens after S1 and S2 commit.
Written by the indexing model from the issue text.
Assessment
- Domain
- databases, distributed-systems
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100