apache/incubator-seata
Voir sur GitHubIs it necessary that both the RM client and the TM client start a timer for reconnecting to seata server ？
Open
#5 338 ouverte le 13 févr. 2023
good first issue
Métriques du dépôt
- Stars
- (25 960 stars)
- Métriques de merge PR
- (Merge moyen 13j 1h) (13 PRs mergées en 30 j)
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);