apache/incubator-seata
Ver no GitHubIs it necessary that both the RM client and the TM client start a timer for reconnecting to seata server ？
Open
#5.338 aberto em 13 de fev. de 2023
good first issue
Métricas do repositório
- Stars
- (25.960 stars)
- Métricas de merge de PR
- (Mesclagem média 13d 1h) (13 fundiu PRs em 30d)
Description
- I have searched the issues of this repository and believe that this is not a duplicate.
Ⅰ. Issue Description
Is it necessary that both rm client and tm client start a timer for reconnecting to seata server？
The log of 2 timeoutCheckers is as follows： 2023-02-13 10:12:51.547 INFO 4079 --- [eoutChecker_1_1] i.s.d.r.k8s.K8sRegistryServiceImpl 2023-02-13 10:12:51.917 INFO 4079 --- [eoutChecker_2_1] i.s.d.r.k8s.K8sRegistryServiceImpl 2023-02-13 10:13:01.547 INFO 4079 --- [eoutChecker_1_1] i.s.d.r.k8s.K8sRegistryServiceImpl 2023-02-13 10:13:01.916 INFO 4079 --- [eoutChecker_2_1] i.s.d.r.k8s.K8sRegistryServiceImpl
io.seata.core.rpc.netty.AbstractNettyRemotingClient#init
public void init() {
timerExecutor.scheduleAtFixedRate(new Runnable() {
@Override
public void run() {
clientChannelManager.reconnect(getTransactionServiceGroup());
}
}, SCHEDULE_DELAY_MILLS, SCHEDULE_INTERVAL_MILLS, TimeUnit.MILLISECONDS);