[
https://issues.apache.org/jira/browse/TEZ-1342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14081118#comment-14081118
]
Jeff Zhang commented on TEZ-1342:
---------------------------------
bq. if one is caught, is clientServer.close() handled properly ? - since the
start is what threw the exception.
clientServer.close() won't fail even if start throw exception, I have
experimented with one using port.
bq. One other suggestion to simplify the test - Specify a port range (maybe 100
ports or so). The RPC layer is supposed to take care of checking whether
required ports are available. The exception check etc won't be required in that
case.
>From a statistics perspective, it is still possible that no available port in
>that range although very unlikely. So I suggest to either successfully start
>with the specified port or throw exception.
> 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)
