You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by "Cameron Lee (Jira)" <ji...@apache.org> on 2021/06/30 23:14:00 UTC

[jira] [Updated] (SAMZA-2654) Allow coordinator url port to be configurable

     [ https://issues.apache.org/jira/browse/SAMZA-2654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Cameron Lee updated SAMZA-2654:
-------------------------------
    Fix Version/s: 1.7

> Allow coordinator url port to be configurable
> ---------------------------------------------
>
>                 Key: SAMZA-2654
>                 URL: https://issues.apache.org/jira/browse/SAMZA-2654
>             Project: Samza
>          Issue Type: Improvement
>            Reporter: Cameron Lee
>            Assignee: Cameron Lee
>            Priority: Major
>             Fix For: 1.7
>
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> Currently, the port for the job coordinator url (for accessing job model) is always dynamically allocated. In some cases, it is helpful to be able to hardcode a port.
> For example, when using Kubernetes, ports only need to be unique within a pod, so port conflict issues are less likely when hardcoding ports. Being able to hardcode a port makes it easier to build the coordinator url since Kubernetes can also set up a "service name" for the coordinator instead of using the physical host name.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)