GitHub user zsp419 added a comment to the discussion: 求助：get global lock fail
> Set `client.rm.lock.retryPolicyBranchRollbackOnConflict=false` in file.conf > (or `seata.client.rm.lock.retry-policy-branch-rollback-on-conflict=false` in > application.yml). > > When this is `true` (default) and multiple branches compete for the same > lock, Seata returns `LockKeyConflictFailFast` which bypasses retry logic (see > `ConnectionProxy.java:356-364`) and immediately throws timeout. > > Setting it to `false` enables the standard retry mechanism (30 retries × 10ms > by default). You can also adjust `client.rm.lock.retryTimes` and > `client.rm.lock.retryInterval` in `/script/client/conf/file.conf`. 谢谢回答，按照您说的改了，现在不会立马报错了，而是按照配置的重试总时长之后报错（我配置的重试次数为60次，每次100ms，总共6s），这是我代码的问题了吗，但是相同的操作， 有些是不报错的，有些是报错的 GitHub link: https://github.com/apache/incubator-seata/discussions/7838#discussioncomment-15191501 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
