Hi! I think that can probably be simplified in the FLIP-6 case:
- All RPC is only between JM and TM and the port should be completely random (optionally within a range). TM and JM discover each other via HA (ZK) or the TM gets the JM RPC port as a parameter when the container is started. (Parameter should be something like 'jobmanager.rpc.ports: 50000-51000') - An exception is the standalone non-HA case, because there is no service-discovery mechanism. That should probably be the a config key like 'standalone.jobmanager.rpc.port: 6123' - The client calls come via HTTP/REST and should have one specific port that may optionally be discovered/redirected via YARN or the dispatchers. /cc Till for your thoughts Best, Stephan On Mon, Sep 25, 2017 at 3:31 PM, Nico Kruber <n...@data-artisans.com> wrote: > Hi Elias, > indeed that looks strange but was introduced with FLINK-3172 [1] with an > argument about using the same configuration key (as opposed to having two > different keys as mentioned) starting at > https://issues.apache.org/jira/browse/FLINK-3172? > focusedCommentId=15091940#comment-15091940 > > > Nico > > [1] https://issues.apache.org/jira/browse/FLINK-3172 > > On Sunday, 24 September 2017 03:04:51 CEST Elias Levy wrote: > > I am wondering why HA mode there is a need for a separate config > parameter > > to set the JM RPC port (high-availability.jobmanager.port) and why this > > parameter accepts a range, unlike jobmanager.rpc.port. > >
