You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@tez.apache.org by "Siddharth Seth (JIRA)" <ji...@apache.org> on 2014/07/30 22:14:40 UTC

[jira] [Commented] (TEZ-1342) tez.am.client.am.port-range not taking effect

    [ https://issues.apache.org/jira/browse/TEZ-1342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14079888#comment-14079888 ] 

Siddharth Seth commented on TEZ-1342:
-------------------------------------

Jeff, the patch looks good. Is it possible to add a simple unit test that verifies that the RPC server is coming up on the required 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.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)