wxrqforever commented on issue #7090: URL: https://github.com/apache/incubator-seata/issues/7090#issuecomment-2567309175
> distributed-lock-table 配置和表都是具备的，分布式锁的表里也是时不时就有数据： ``` #Transaction storage configuration, only for the server. The file, db, and redis configuration values are optional. store.mode=db store.lock.mode=db store.session.mode=db #These configurations are required if the `store mode` is `db`. If `store.mode,store.lock.mode,store.session.mode` are not equal to `db`, you can remove the configuration block. store.db.datasource=druid store.db.dbType=mysql store.db.driverClassName=com.mysql.jdbc.Driver store.db.url=xxxxx store.db.user=xxxxx store.db.password= xxxxx store.db.minConn=5 store.db.maxConn=30 store.db.globalTable=global_table store.db.branchTable=branch_table store.db.distributedLockTable=distributed_lock store.db.vgroupTable=vgroup-table store.db.queryLimit=100 store.db.lockTable=lock_table store.db.maxWait=5000 ``` 我推测了一下，怀疑是这样的，这两个实例启动定时任务的时机有些差别，如上面日志所示，可能相差有8秒，目前配置的超时时间是1秒，而执行重试又跑的很快，所以并不是分布式锁没生效，而是两个实例都正常获取到了上一次实例跑完释放的锁了。 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@seata.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: notifications-unsubscr...@seata.apache.org For additional commands, e-mail: notifications-h...@seata.apache.org
