You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@rocketmq.apache.org by "unbridled-41 (via GitHub)" <gi...@apache.org> on 2026/10/09 21:02:30 UTC
[I] [Bug] The Studio and client defaults still address the NameServer by its ambiguous service name [rocketmq-dashboard]
unbridled-41 opened a new issue, #5972:
URL: https://github.com/apache/rocketmq-dashboard/issues/5972
### Studio Version
branch: `rocketmq-studio` @ `7e7aa344`
### Runtime Environment
`docker compose --env-file deploy/.env.example -f deploy/docker-compose.yml config`.
### Describe the Bug
The runbook records an observed failure (2026-09-17): on the shared `rocketmq_net`, the service name `nameserver` resolved to more than one A record, so a container could talk to another stack's NameServer. Its prescription is to use the unique container name `rmq-nameserver:9876`, and it lists the four `NAMESRV_ADDR` values, the two broker configs and the proxy config - all fixed in the tree. Three defaults were left behind: `deploy/docker-compose.yml`'s `STUDIO_ROCKETMQ_NAMESRV_ADDR` default (the Studio server itself, whose views would then show foreign brokers), the two `NAMESRV_ADDR` fallbacks in `deploy/rocketmq/clients/Trace{Producer,Consumer}.java`, and the README's description of `rmq-proxy.json`. The `STUDIO_ROCKETMQ_NAMESRV_ADDR` knob was also the only way to change that address and was missing from `deploy/.env.example`.
### Steps to Reproduce
`docker compose -f deploy/docker-compose.yml config | grep NAMESRV` shows `nameserver:9876` before the fix.
### What Did You Expect to See?
The unique container name everywhere, and the override documented.
### What Did You See Instead?
The ambiguous service name in three defaults, and an undocumented knob.
### Impact
On a host that also runs a second stack on the shared network, Studio can resolve another stack's NameServer and show foreign brokers, with no obvious cause.
### Acceptance Criteria
Every default that names the NameServer uses the unique container name, the override is documented in the env template, and the compose file still validates.
**Corresponding PR:** #ISSUEPR#
--
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.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Bug] The Studio and client defaults still address the NameServer by its ambiguous service name [rocketmq-dashboard]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] closed issue #5972: [Bug] The Studio and client defaults still address the NameServer by its ambiguous service name
URL: https://github.com/apache/rocketmq-dashboard/issues/5972
--
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
Re: [I] [Bug] The Studio and client defaults still address the NameServer by its ambiguous service name [rocketmq-dashboard]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #5972:
URL: https://github.com/apache/rocketmq-dashboard/issues/5972#issuecomment-6330325409
This issue has been automatically closed because there has been no activity for 7 days. If you believe this issue is still relevant, please reopen it with updated information.
--
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