apache / apache/incubator-seata
事务回滚发生死锁
- Dominant language
- Java
- Stars
- 26k
- Forks
- 8.8k
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 4
Description
- [ ] I have searched the [issues](https://github.com/seata/seata/issues) of this repository and believe that this is not a duplicate.
### Ⅰ. Issue Description
事务回滚发生死锁
### Ⅱ. Describe what happened
### Ⅲ. Describe what you expected to happen
### Ⅳ. How to reproduce it (as minimally and precisely as possible)
偶发性,本地尝试无法重现
### Ⅴ. Anything else we need to know?
### Ⅵ. Environment:
- JDK version :1.8
- OS : centos7
- seata: 1.3.0
- mysql是阿里云的rds 5.7.14-AliSQL-X-Cluster-1.5.0.3-20191128-log
- mysql 隔离级别 READ-COMMITTED
- seata的数据源代理设置 seata.enable-auto-data-source-proxy=false
Contributor guide
Research direction
The report names no source files, tests, or reproducible entry point. Begin by reviewing the deadlock screenshots and the Seata 1.3.0, JDK 8, and MySQL RDS environment, then capture a minimal reproduction; done means identifying the rollback deadlock cause and documenting a verified fix or regression test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, mysql
- Domain
- databases, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 18/100