Skip to content
Discussion options

You must be logged in to vote

It depends on how your Proxy is deployed.

  • Local mode (Proxy runs inside the broker): gRPC consumers are registered in the broker, so mqadmin works as usual.
  • Cluster mode (separate Proxy): gRPC consumers are registered only in the Proxy. The Proxies share them with each other, but they are never sent to the brokers. mqadmin consumerConnection -g <group> asks a broker, so it says the group is not online.

What you can do in cluster mode:

  1. Connections: point mqadmin at the Proxy's remoting port (default 8080, not the gRPC port 8081). The Proxy answers this request from its own consumer table:

    sh mqadmin consumerConnection -n <namesrv> -g <group> -b <proxyHost>:8080
  2. Lag / progress: sh mqa…

Replies: 1 comment 2 replies

Comment options

You must be logged in to vote
2 replies
@zhhisabugs
Comment options

@zhhisabugs
Comment options

Answer selected by zhhisabugs
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants