[GitHub] [rocketmq-operator] hzliangbin commented on issue #17: why use ip for nameserver

[GitBox <gi...@apache.org>]

hzliangbin commented on issue #17:
URL: https://github.com/apache/rocketmq-operator/issues/17#issuecomment-631306482


   @duhenglucky @Kaijun According to the blog of  AliMiddleware, the nameserver cluster  is decentralization. And each broker will connect to all nameservers to refresh broker's info. It's OK when NameServer' size is 1. kubernetes service will always lead to one backend pod. 
   
   But  when there are 2 or more nameservers, the kubernetes service will forward to  only one of the backend pods based on some loadbanlance strategy. 
   
   A not that perfect solution :
   if you have 3 nameservers you should create 3 services. Each service targets exactly one pod. The brokers use servicename instead IP to register to namerservers. 
   


----------------------------------------------------------------
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