[Bug][TubeMQ] After running for a period of time, it has been unable to connect to the broker

[mrcat2018]

What happened

I use tubemq-client-go to consume tubemq's msg. After running for a period of time, it has been unable to connect to the broker. The phenomenon of not being able to connect to the broker lasted for 8 hours, and it was connected after restarting the process.

go mod version is github.com/apache/incubator-inlong/inlong-tubemq/tubemq-client-twins/tubemq-client-go v0.0.0-20220311090829-1838ba3eb272。

The key log is as follows：

2022-07-28 11:44:23.548 INFO client/consumer_impl.go:249 [CONSUMER]GetMessage error code: 5, msg:dial tcp xxx.xxx.xx.xx:8123: connect: connection refused
2022-07-28 11:44:24.155 INFO client/consumer_impl.go:249 [CONSUMER]GetMessage error code: 5, msg:dial tcp xx.xxx.xxx.xx:8123: connect: connection refused
2022-07-28 11:44:24.947 INFO client/consumer_impl.go:249 [CONSUMER]GetMessage error code: 5, msg:dial tcp xxx.xxx.xx.xx:8123: connect: connection refused
2022-07-28 11:44:25.556 INFO client/consumer_impl.go:249 [CONSUMER]GetMessage error code: 5, msg:dial tcp xx.xxx.xxx.xx:8123: connect: connection refused
2022-07-28 11:44:26.148 INFO client/consumer_impl.go:249 [CONSUMER]GetMessage error code: 5, msg:dial tcp xxx.xxx.xx.xx:8123: connect: connection refused
2022-07-28 11:44:26.957 INFO client/consumer_impl.go:249 [CONSUMER]GetMessage error code: 5, msg:dial tcp xx.xxx.xxx.xx:8123: connect: connection refused
2022-07-28 11:44:27.346 INFO client/consumer_impl.go:249 [CONSUMER]GetMessage error code: 5, msg:dial tcp xxx.xxx.xx.xx:8123: connect: connection refused
2022-07-28 11:44:28.355 INFO client/consumer_impl.go:249 [CONSUMER]GetMessage error code: 5, msg:dial tcp xx.xxx.xxx.xx:8123: connect: connection refused
11:44:28.355 INFO client/consumer_impl.go:249 [CONSUMER]GetMessage error code: 5, msg:dial tcp xx.xxx.xxx.xx:8123: connect: connection refused
2022-07-28 11:44:32.859 ERROR client/heartbeat.go:103 consumer hb err code: 2, msg:exceptionName:"org.apache.tubemq.corerpc.exception.StandbyException" stackTrace:"xxxxx:8609 is not master now. the connecting client id is xxx_xxx_xxx.-25120-1657705121000-1-go-0.1.1"

What you expected to happen

The master-slave switch can connect to the broker normally.

How to reproduce

I dont know.
In this case, it has been unable to connect after more than 2 months of running.

Environment

os is centos 7
go mod version is github.com/apache/incubator-inlong/inlong-tubemq/tubemq-client-twins/tubemq-client-go v0.0.0-20220311090829-1838ba3eb272。

InLong version

master

InLong Component

InLong TubeMQ

Are you willing to submit PR?

• Yes, I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[gosonzhang]

@mrcat2018, thanks for your contribution!!