Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

服务A顺序调用服务B/C,最后完成本地事务。当服务C中的Confirm发生异常,服务B中的数据没有回滚。 #120

Open
liangzijin opened this issue May 10, 2019 · 1 comment

Comments

@liangzijin
Copy link

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

settings
which type of idempotent support you use?(framework idempotent/business idempotent?)

which version and component do you use( redis/rdb log implement and redis/rdb version? kafka/ons queue implements and queue version? ribbon/dubbo rpc implements?)

**the relative records **
records in table executed_trans, idempotent, logs(trans_log_detail, trans_log_unfinished,or redis records)

can you reproduce it in demos by changing certain settings
this will help us understand the situation more effectively

Additional context
Add any other context about the problem here.

@skyesx
Copy link
Contributor

skyesx commented May 10, 2019

TCC理念如此,可以先熟悉下理论,Confirm失败只会重试

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants