Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TubeMQ consumers configure the wrong standby masterIP and set it to the first,consumers will throw exceptions. #103

Closed
Libeibei1990 opened this issue Oct 31, 2019 · 1 comment · Fixed by #104

Comments

@Libeibei1990
Copy link

TubeMQ consumers configure the wrong standby masterIP and set it to the first,consumers will throw exceptions. And then,consumers re-register successfully after 5min.

The reason for this problem is because consumers don‘t poll connection list if the connection times out.

[ERROR] [BaseMessageConsumer] Register to master failed.
java.util.concurrent.TimeoutException
at com.tencent.tubemq.corerpc.client.CallFuture.get(CallFuture.java:139)
at com.tencent.tubemq.corerpc.netty.NettyClient.call(NettyClient.java:157)
at com.tencent.tubemq.corerpc.RpcServiceFailoverInvoker.callMethod(RpcServiceFailoverInvoker.java:69)
at com.tencent.tubemq.corerpc.AbstractServiceInvoker.invoke(AbstractServiceInvoker.java:57)
at com.sun.proxy.$Proxy0.consumerRegisterC2M(Unknown Source)
at com.tencent.tubemq.client.consumer.BaseMessageConsumer.startMasterAndBrokerThreads(BaseMessageConsumer.java:563)
at com.tencent.tubemq.client.consumer.BaseMessageConsumer.completeSubscribe(BaseMessageConsumer.java:306)
at com.tencent.tubemq.client.consumer.SimplePushMessageConsumer.completeSubscribe(SimplePushMessageConsumer.java:76)

@gosonzhang
Copy link
Collaborator

Thank you, you are right. When the request to the Master is abnormal, it need to try to poll other nodes, so that the client can quickly connect to the active node.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants