QNJR-GROUP / EasyTransaction

A distribute transaction solution(分布式事务) unified the usage of TCC , SAGA ,FMT (seata/fescar AutoCompensation), reliable message, compensate and so on;
Apache License 2.0
2.36k stars 809 forks source link

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

Open liangzijin opened 5 years ago

liangzijin commented 5 years ago

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 commented 5 years ago

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