[
https://issues.apache.org/jira/browse/TEZ-1342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14081416#comment-14081416
]
Siddharth Seth commented on TEZ-1342:
-------------------------------------
So it sounds like the options are
1) Check port up front
2) Use a port-range
3) 10 iterations
[~hitesh] just mentioned that checking ports on a jenkins host is a race in
anycase, since that's running multiple jobs.
If we're going with Option 3 - please ensure that at least one instance of the
server comes up on the right port.
> tez.am.client.am.port-range not taking effect
> ---------------------------------------------
>
> Key: TEZ-1342
> URL: https://issues.apache.org/jira/browse/TEZ-1342
> Project: Apache Tez
> Issue Type: Bug
> Affects Versions: 0.5.0
> Reporter: Johannes Zillmann
> Assignee: Jeff Zhang
> Attachments: Tez-1342-2.patch, Tez-1342.patch
>
>
> Controlling the ports of Tez' Application Master via
> 'tez.am.client.am.port-range' does not seem to work.
> When setting this on the client side, i can see its properly picked up by the
> DAGClientServer, but then port used is still not within that range!
--
This message was sent by Atlassian JIRA
(v6.2#6252)
