Tried this out (with Hadoop-2.4 libraries included with Tez); I see the same behaviour where the port range config is being completely ignored; the correct value is available in the DAGClientServer. @Johannes, could you please open a TEZ jira - so that we can track this for Tez. On the Hadoop side - for one thing, better documentation is required on how this parameter needs to be specified. This is used by the MapReduce AppMaster as well - and as far as I know does work. This does need verification though.
@Jeff, I believe this value is supposed to be used when starting up the RPC server - once that is setup, we fetch the relevant port information and register it with the RM so that the Client gets it in an application report. 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
