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 2021/05/14 13:00:20 UTC
[GitHub] [rocketmq] z5614036 opened a new issue #2894: kafka已经祛除zk了,rocketmq以后会把nameserver砍掉吧,多部署一个就增加一些麻烦
z5614036 opened a new issue #2894:
URL: https://github.com/apache/rocketmq/issues/2894
kafka已经祛除zk了,rocketmq能跟进吗?
--
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] duhenglucky closed issue #2894: kafka已经祛除zk了,rocketmq以后会把nameserver砍掉吧,多部署一个就增加一些麻烦
Posted by GitBox <gi...@apache.org>.
duhenglucky closed issue #2894:
URL: https://github.com/apache/rocketmq/issues/2894
--
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] duhenglucky commented on issue #2894: kafka已经祛除zk了,rocketmq以后会把nameserver砍掉吧,多部署一个就增加一些麻烦
Posted by GitBox <gi...@apache.org>.
duhenglucky commented on issue #2894:
URL: https://github.com/apache/rocketmq/issues/2894#issuecomment-841919642
@z5614036 这个建议涉及到的架构改动比较大,所以最好咱们再dev@rocketmq.apache.org,users@rocketmq.apache.org 里面先讨论下。这里面有个前提就是先搜集下nameserver 是不是真的给运维带来了很大负担,或者去掉zk 后的运维负担是不是更重?毕竟 name server 是很轻的,不同于zk。
--
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] vongosling commented on issue #2894: kafka已经祛除zk了,rocketmq以后会把nameserver砍掉吧,多部署一个就增加一些麻烦
Posted by GitBox <gi...@apache.org>.
vongosling commented on issue #2894:
URL: https://github.com/apache/rocketmq/issues/2894#issuecomment-841938453
Why we would follow others' action? RocketMQ has its own design philosophy, if you follow the latest RIP about architecture updates, you could have a better understanding of the fact that we have better and more tangible improvements in data management.
--
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] duhenglucky closed issue #2894: kafka已经祛除zk了,rocketmq以后会把nameserver砍掉吧,多部署一个就增加一些麻烦
Posted by GitBox <gi...@apache.org>.
duhenglucky closed issue #2894:
URL: https://github.com/apache/rocketmq/issues/2894
--
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] vongosling edited a comment on issue #2894: kafka已经祛除zk了,rocketmq以后会把nameserver砍掉吧,多部署一个就增加一些麻烦
Posted by GitBox <gi...@apache.org>.
vongosling edited a comment on issue #2894:
URL: https://github.com/apache/rocketmq/issues/2894#issuecomment-841938453
Why should we follow other guys' actions? RocketMQ has its own design philosophy, if you follow the latest RIP about architecture updates, you could have a better understanding of the fact that we have better and more tangible improvements in data management.
--
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] duhenglucky commented on issue #2894: kafka已经祛除zk了,rocketmq以后会把nameserver砍掉吧,多部署一个就增加一些麻烦
Posted by GitBox <gi...@apache.org>.
duhenglucky commented on issue #2894:
URL: https://github.com/apache/rocketmq/issues/2894#issuecomment-841919642
@z5614036 这个建议涉及到的架构改动比较大,所以最好咱们再dev@rocketmq.apache.org,users@rocketmq.apache.org 里面先讨论下。这里面有个前提就是先搜集下nameserver 是不是真的给运维带来了很大负担,或者去掉zk 后的运维负担是不是更重?毕竟 name server 是很轻的,不同于zk。
--
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] vongosling edited a comment on issue #2894: kafka已经祛除zk了,rocketmq以后会把nameserver砍掉吧,多部署一个就增加一些麻烦
Posted by GitBox <gi...@apache.org>.
vongosling edited a comment on issue #2894:
URL: https://github.com/apache/rocketmq/issues/2894#issuecomment-841938453
Why should we follow other guys' actions? RocketMQ has its own design philosophy, if you follow the latest RIP about architecture updates, you could have a better understanding of the fact that we have better and more tangible improvements in data management.
--
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] vongosling commented on issue #2894: kafka已经祛除zk了,rocketmq以后会把nameserver砍掉吧,多部署一个就增加一些麻烦
Posted by GitBox <gi...@apache.org>.
vongosling commented on issue #2894:
URL: https://github.com/apache/rocketmq/issues/2894#issuecomment-841938453
Why we would follow others' action? RocketMQ has its own design philosophy, if you follow the latest RIP about architecture updates, you could have a better understanding of the fact that we have better and more tangible improvements in data management.
--
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