You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@rocketmq.apache.org by GitBox <gi...@apache.org> on 2020/09/18 08:03:54 UTC
[GitHub] [rocketmq-operator] stheart opened a new issue #52: Broker does not support initiating registration to a newly created nameserver
stheart opened a new issue #52:
URL: https://github.com/apache/rocketmq-operator/issues/52
Question
we use rocketmq-operator to deploy in k8s,found that when up-scale name server cluster,broker will restart one by one.
I check the broker code, it seems that broker can't refresh name server address list automatic when add new name server pod, so operator has to restart all broker.
FEATURE REQUEST
broker support register to new name server pod,don't need to restart.
for example
1.broker provide api to refresh name server address
2.rocketmq-operator push the new name server address to broker api when add new nameserver pod.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [rocketmq-operator] liuruiyiyang commented on issue #52: Broker does not support initiating registration to a newly created nameserver
Posted by GitBox <gi...@apache.org>.
liuruiyiyang commented on issue #52:
URL: https://github.com/apache/rocketmq-operator/issues/52#issuecomment-695779618
Yes, the broker does not support hot-change the name server IP list yet (at lease in version 4.5.0), so currently our solution is to restart them one by one. And users can choose not to restart in Broker CR by setting ```allowRestart```. In fact we have some discussion on this, checkout RocketMQ PR#1458 https://github.com/apache/rocketmq/pull/1458 . We will continue to look at this issue.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [rocketmq-operator] liuruiyiyang commented on issue #52: Broker does not support initiating registration to a newly created nameserver
Posted by GitBox <gi...@apache.org>.
liuruiyiyang commented on issue #52:
URL: https://github.com/apache/rocketmq-operator/issues/52#issuecomment-695779618
Yes, the broker does not support hot-change the name server IP list yet (at lease in version 4.5.0), so currently our solution is to restart them one by one. And users can choose not to restart in Broker CR by setting ```allowRestart```. In fact we have some discussion on this, checkout RocketMQ PR#1458 https://github.com/apache/rocketmq/pull/1458 . We will continue to look at this issue.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org