- 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);
2条答案
按热度按时间wyyhbhjk1#
Since the channels of RM and TM will not be shared, both will perform a reconnection detection, of course, this piece can be optimized
hgb9j2n62#
I want to try and see if I can solve this, can you assign it to me?