[ https://issues.apache.org/jira/browse/TEZ-1342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14080333#comment-14080333 ]
Siddharth Seth commented on TEZ-1342: ------------------------------------- Comments on the patch - Missing Apache header on the test - 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. - Don't think 10 iterations are required. One should be enough ? > 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)