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
logTable 配置不生效 #4413
Comments
请提供一下seata版本以及配置log table的方式方便排查,此外确认一下配置的undolog表中是否有数据 |
配置中心为nacos,seata相关的配置应该放到nacos上吧? |
是放在nacos上的,为了方便截图,我取下来了 |
nacos配置时带seata前缀吗?如果是,请尝试去掉seata前缀试试。如:client.undo.logTable=undo_log |
貌似是这里取的表名:io.seata.rm.datasource.undo.AbstractUndoLogManager#UNDO_LOG_TABLE_NAME |
tmd,本地bebug就是不跑删除语句,日了狗了 |
可以试试debug一下,相关代码
|
删除是延迟异步的操作,若要debug可以执行一个dml语句,然后AbstractUndoLogManager#flushUndoLogs打断点,这一步会将前后镜像的undo_log持久化,使用的logtable与delete相同 |
哪seata配置下的表名有啥用啊 |
而且dataId也不支持环境变量,我想每个服务块都用不同的表名咋办 |
1.4.2版本开始支持从一个Nacos dataId中获取所有配置信息,具体配置详情可参考官网 |
这个我配了,但是properties文件貌似不支持环境变量,如果我想每个服务都用不同的表名咋办 |
|
估计重复的会被覆盖,你也可以提一个PR改正 |
这个问题呢 |
若是服务之间需要不同的配置,可以设置不同的nacos的dataId来实现吧(提供一个思路,这一块我了解的不多 |
Ⅰ. Issue Description
Ⅱ. Describe what happened
启动获取变量正常,删除sql执行的是默认的
If there is an exception, please attach the exception trace:
Ⅲ. Describe what you expected to happen
Ⅳ. How to reproduce it (as minimally and precisely as possible)
Ⅴ. Anything else we need to know?
Ⅵ. Environment:
The text was updated successfully, but these errors were encountered: