You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by GitBox <gi...@apache.org> on 2021/05/04 01:50:46 UTC

[GitHub] [samza] kw2542 edited a comment on pull request #1499: SAMZA-2654: Allow coordinator url port to be configurable

kw2542 edited a comment on pull request #1499:
URL: https://github.com/apache/samza/pull/1499#issuecomment-831638558


   > More context about how this can be used:
   > When using Kubernetes, we can create a "Service" which provides a consistent coordinator url, even when the job coordinator switches pods. The port is one piece of information needed to create this "Service". If we want to use a Kubernetes controller to create the "Service" (per the Kubernetes operator pattern), then we don't need to retrieve the port from the job coordinator in order to create the "Service".
   
   This may not bring a lot of benefit, especially for portable beam jobs, as there are multiple port numbers need to be communicated between JC Pod and Worker Pod and preconfigure all of them may not be practical.
   
   Is this just for ease of creating "Service" or w/o predefined port number, we cannot create "Service" at all?
   


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