You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@seata.apache.org by "XiaoFeiASK (via GitHub)" <gi...@apache.org> on 2026/09/28 02:31:06 UTC
[I] [BUG] RM resource re-registration may be sent to the wrong TC in multi-TC clusters [incubator-seata-go]
XiaoFeiASK opened a new issue, #1203:
URL: https://github.com/apache/incubator-seata-go/issues/1203
### ✅ 验证清单
- [x] 🔍 我已经搜索过 [现有 Issues](https://github.com/apache/incubator-seata-go/issues)，确信这不是重复问题
- [x] 🛠️ 我愿意自己处理这个议题
### 🚀 Go 版本
1.23.0
### 📦 Seata-go 版本
v1.2.0
### 💾 操作系统
🍎 macOS
### 📝 Bug 描述
### What happens
When an RM reconnects in a multi-TC cluster, it re-registers its cached resources. However, the registration request is sent through the client's shared connection pool and may be routed to a different TC from the one whose session has just reconnected.
Because the receiving TC associates the resource IDs with the connection that delivered the request, the reconnected TC may still lack the resource-to-RM session mapping. Re-registration can therefore appear to succeed without restoring that mapping on the intended TC.
### Error information
There is no confirmed, consistent error message for this multi-TC scenario. The issue concerns which connection receives the registration request, rather than a failure to send the request.
### Impact
RM resource registration after reconnect is not guaranteed to restore the mapping on the reconnected TC in a multi-TC deployment. The registration request should be sent through the newly opened session or channel.
Related: #128 and PR #1195.
### 🔄 重现步骤
1. Configure an RM to connect to at least two TC servers, TC-A and TC-B, and register a resource.
2. Disconnect the RM session on TC-A, then allow it to reconnect while the session on TC-B remains available.
3. Observe where the RM's resource re-registration request is sent. Because session selection is load-balanced, it may be sent to TC-B.
### ✅ 预期行为
The resource is re-registered through the newly reconnected session on TC-A, restoring its resource-to-session mapping there.
### ❌ 实际行为
The request may be sent to TC-B instead. In that case, TC-A's mapping is not restored, even if the registration request succeeds.
### 💡 可能的解决方案
Pass the newly opened session or channel to the re-registration path and send the request through that connection. Cover the routing behavior with a multi-TC test.
--
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-unsubscribe@seata.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@seata.apache.org
For additional commands, e-mail: notifications-help@seata.apache.org
Re: [I] [BUG] RM resource re-registration may be sent to the wrong TC in multi-TC clusters [incubator-seata-go]
Posted by "thunguo (via GitHub)" <gi...@apache.org>.
thunguo closed issue #1203: [BUG] RM resource re-registration may be sent to the wrong TC in multi-TC clusters
URL: https://github.com/apache/incubator-seata-go/issues/1203
--
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-unsubscribe@seata.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@seata.apache.org
For additional commands, e-mail: notifications-help@seata.apache.org
Re: [I] [BUG] RM resource re-registration may be sent to the wrong TC in multi-TC clusters [incubator-seata-go]
Posted by "XiaoFeiASK (via GitHub)" <gi...@apache.org>.
XiaoFeiASK commented on issue #1203:
URL: https://github.com/apache/incubator-seata-go/issues/1203#issuecomment-5862265138
please assign to me
--
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-unsubscribe@seata.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@seata.apache.org
For additional commands, e-mail: notifications-help@seata.apache.org