You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@rocketmq.apache.org by "ProfutW (via GitHub)" <gi...@apache.org> on 2024/07/12 09:49:54 UTC

[D] gRPC SDK连接服务端后,AdminTool似乎不支持对特定消费者的消息查询和重发 [rocketmq]

GitHub user ProfutW created a discussion: gRPC SDK连接服务端后,AdminTool似乎不支持对特定消费者的消息查询和重发

按照官方文档部署5.2.0版本的服务端后,我使用对应版本的gRPC SDK连接服务端,在SDK层面的消息收发一切正常,但是dashboard无法检测到正常消费的消息情况,如下图:
![image](https://github.com/user-attachments/assets/64141251-ba25-4428-a1a0-99a1fa50506b)
但实际上test_consumer是在线的:
![image](https://github.com/user-attachments/assets/5b0c6a1e-4e30-441d-bd51-838acd42adfe)

接着我使用AdminTool进行排查,发现由于gRPC连接的是proxy,所以mqadmin consumerConnection指定namesrv时需要给proxy的地址,而不是namesrv的地址,如下:
![image](https://github.com/user-attachments/assets/54ca2bfa-870e-414a-ba6b-3665be322d18)

然后我又使用queryMsgByUniqueKey查询指定client的消息,出现如下报错:
![image](https://github.com/user-attachments/assets/911f895c-f69d-4597-ae1f-c014d3c8c6c7)

接着我换了remoting SDK,其他配置一模一样,使用namesrv进行查询就能得到到对应的消息:
![image](https://github.com/user-attachments/assets/a363ea0b-1e4d-4ec7-b00e-825108320a77)

同样,dashboard也正常了:
![image](https://github.com/user-attachments/assets/66f2665c-e625-4076-8160-2ef9f75f0e20)

综上,似乎AdminTool和dashboard都没有对使用gRPC连接的情况进行完整的支持,我理解起码AdminTool需要能够支持这一功能
或者说是有什么配置不正确导致的这一问题,希望各位指正
谢谢!

GitHub link: https://github.com/apache/rocketmq/discussions/8386

----
This is an automatically sent email for dev@rocketmq.apache.org.
To unsubscribe, please send an email to: dev-unsubscribe@rocketmq.apache.org