apache/incubator-seata
Vedi su GitHubIs it necessary that both the RM client and the TM client start a timer for reconnecting to seata server ？
Open
#5338 aperta il 13 feb 2023
good first issue
Metriche repository
- Star
- (25.960 star)
- Metriche merge PR
- (Merge medio 13g 1h) (13 PR mergiate in 30 g)
Descrizione
- 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);