You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@skywalking.apache.org by GitBox <gi...@apache.org> on 2019/02/13 05:54:37 UTC

[GitHub] wu-sheng opened a new pull request #2244: Support to register different host/port at cluster coordinator

wu-sheng opened a new pull request #2244: Support to register different host/port at cluster coordinator
URL: https://github.com/apache/incubator-skywalking/pull/2244
 
 
   According to #2217 , in some scenarios, the oap server binding address is not suitable for oap cluster internal communication. So, need a different address register at cluster coordinator, like zookeeper and consul.
   
   In #2218, providing another host/port in core module could solve this issue, but could make more confuse, because this is a special case, and most people wouldn't use this. Also, not all cluster management implementation supports in this way, such as k8s.
   
   In this pull request, I add two optional settings in zookeeper and consul cluster coordinator.
   - internalComHost
   - internalComPort
   
   Default they are inactive, if you active them manually, the coordinator use these to notify other oap node, when they do internal communication, to instead `gRPCHost` and `gRPCPort`.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on 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


With regards,
Apache Git Services