Is it necessary that both the RM client and the TM client start a timer for reconnecting to seata server ？ · apache/incubator-seata#5338

(2 留言) (0 反應) (1 負責人)Java (25,960 star) (8,878 fork)batch import

good first issue

描述

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);

貢獻者指南

技術棧: java
領域: backenddatabase
議題類型: refactor
難度: 3
預計時間: 1-3 hours
活動狀態: active
清晰度: clear
前置要求: Basic understanding of Seata's architectureFamiliarity with Java and Netty
新手友善度: 40
研究方向: Investigate whether both RM client and TM client need separate reconnect timers. The issue points to `io.seata.core.rpc.netty.AbstractNettyRemotingClient#init` where a single timer is scheduled. Review the code to see if both clients share this class or have separate instances. Consider consolidating into one timer if appropriate, or document why two are needed. Check related comments in the issue for maintainer feedback.