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/06/09 16:19:09 UTC
[GitHub] [rocketmq-operator] keranbingaa opened a new issue #28: question about namesrv cluster up-scale
keranbingaa opened a new issue #28:
URL: https://github.com/apache/rocketmq-operator/issues/28
when namesrv cluster up-scaling，does the broker shutdown and change the namesrv list and then restart?
I have this question becuase I note the broker IP changed after namesrv cluster up-scale and the log file contians restart log. can we up-scale the namesrv cluster without restart broker?
----------------------------------------------------------------
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] keranbingaa commented on issue #28: question about namesrv cluster up-scale
Posted by GitBox <gi...@apache.org>.
keranbingaa commented on issue #28:
URL: https://github.com/apache/rocketmq-operator/issues/28#issuecomment-668979795
> In fact we working on this and you can refer to RocketMQ PR#1458[https://github.com/[apache/rocketmq/pull/1458](https://github.com/apache/rocketmq/pull/1458)]
ok,I will refer to this
----------------------------------------------------------------
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 closed issue #28: question about namesrv cluster up-scale
Posted by GitBox <gi...@apache.org>.
liuruiyiyang closed issue #28:
URL: https://github.com/apache/rocketmq-operator/issues/28
----------------------------------------------------------------
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 #28: question about namesrv cluster up-scale
Posted by GitBox <gi...@apache.org>.
liuruiyiyang commented on issue #28:
URL: https://github.com/apache/rocketmq-operator/issues/28#issuecomment-668958231
In fact we have considered this question and you can refer to RocketMQ PR#1458[https://github.com/apache/rocketmq/pull/1458]
----------------------------------------------------------------
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 #28: question about namesrv cluster up-scale
Posted by GitBox <gi...@apache.org>.
liuruiyiyang commented on issue #28:
URL: https://github.com/apache/rocketmq-operator/issues/28#issuecomment-662288997
YES, when namesrv cluster up-scaling, the broker instances will rolling restart (one by one). Thus this process has little influence on providing service for user bussiness.
Could you please tell us more about what harms if the broker restart in your application scenario?
----------------------------------------------------------------
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 edited a comment on issue #28: question about namesrv cluster up-scale
Posted by GitBox <gi...@apache.org>.
liuruiyiyang edited a comment on issue #28:
URL: https://github.com/apache/rocketmq-operator/issues/28#issuecomment-662288997
YES, when namesrv cluster up-scaling, the broker instances will rolling restart (one by one). Thus this process has little influence on providing service for user bussiness.
Could you please tell us more about what harms if the broker restart(broker IP changing) in your application scenario?
----------------------------------------------------------------
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 edited a comment on issue #28: question about namesrv cluster up-scale
Posted by GitBox <gi...@apache.org>.
liuruiyiyang edited a comment on issue #28:
URL: https://github.com/apache/rocketmq-operator/issues/28#issuecomment-668958231
In fact we working on this and you can refer to RocketMQ PR#1458[https://github.com/apache/rocketmq/pull/1458]
----------------------------------------------------------------
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 closed issue #28: question about namesrv cluster up-scale
Posted by GitBox <gi...@apache.org>.
liuruiyiyang closed issue #28:
URL: https://github.com/apache/rocketmq-operator/issues/28
----------------------------------------------------------------
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 edited a comment on issue #28: question about namesrv cluster up-scale
Posted by GitBox <gi...@apache.org>.
liuruiyiyang edited a comment on issue #28:
URL: https://github.com/apache/rocketmq-operator/issues/28#issuecomment-662288997
YES, when namesrv cluster up-scaling, the broker instances will rolling restart (one by one). Thus this process has little influence on providing service for user bussiness, unless you have only one broker instance.
Could you please tell us more about what harms if the broker restart(broker IP changing) in your application scenario?
----------------------------------------------------------------
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