[
https://issues.apache.org/jira/browse/TEZ-1342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14080511#comment-14080511
]
Jeff Zhang commented on TEZ-1342:
---------------------------------
[[email protected]]
bq. It's possible that the port selected is already in use - which can cause
random test failures. It'd be better if the port generated is checked in the
test before attempting to start a server.
That's why I add an exception check. So that means either the server can start
successfully listening on that port or failed because of not available port.
bq. Don't think 10 iterations are required. One should be enough ?
Because there are 2 results as described above, I make 10 iterations to cover
both cases.
But you may be right that checking the port before test may be a better way.
Because even 10 iterations may not cover both cases.
> 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)
