You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@rocketmq.apache.org by "RockteMQ-AI (via GitHub)" <gi...@apache.org> on 2026/08/07 11:12:07 UTC

Re: [I] 是否需要单独部署controller [rocketmq-operator]

RockteMQ-AI commented on issue #149:
URL: https://github.com/apache/rocketmq-operator/issues/149#issuecomment-5216294815

   **Issue Evaluation**
   
   Category: `question` | Status: **Answered**
   
   The RocketMQ 5.x controller (DLedger-based controller mode) replaces the traditional NameServer for broker registration and routing. Whether you need to deploy it separately depends on your deployment mode:
   
   - **NameServer mode (default):** No controller needed. NameServer handles routing.
   - **Controller mode (5.x):** Yes, you need to deploy the controller separately. The controller provides broker registration, routing, and failover coordination. It uses DLedger for consensus.
   
   The operator's support for controller mode is tracked in issue #133. Until that is implemented, you may need to deploy the controller manually alongside the operator-managed cluster.
   
   ---
   *Automated evaluation by @RockteMQ-AI*
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@rocketmq.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org