Hi Johannes,
setPortRangeConfig is for setting the port range for RPC server which has
its own threads ( including listener, handlers ). DAGClientServer is in
another thread which is not shared with thread of RPC server. Check the
following code in DAGClientServer.java, we will get the bindAddress ( host
& port ) and register it to RM (YarnTaskSchedulerService). Then the client
could get the bindAddress by getting ApplicationReport (DAGClientRPCImpl),
and then use it to connect to AM. Let me know if it is still not clear for
you.
// DAGClientServer.java
server.start();
bindAddress = NetUtils.getConnectAddress(server);
LOG.info("Instantiated DAGClientRPCServer at " + bindAddress);
Best Regards,
Jeff Zhang
On Tue, Jul 29, 2014 at 6:29 AM, Johannes Zillmann <[email protected]
> wrote:
> Question about 'tez.am.client.am.port-range’.
>
> Seems to have no effect setting this before client initialization.
> Debugged DAGClientServer and the setting comes through properly and is
> handed over to new RPC.Builder(conf)….setPortRangeConfig()...build()
>
> So i’m guessing this is a bug with the RPC lib !? Can anybody confirm ?
>
> Johannes
--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you are hereby notified that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender immediately
and delete it from your system. Thank You.
