You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@reef.apache.org by "Markus Weimer (JIRA)" <ji...@apache.org> on 2015/04/13 20:16:14 UTC

[jira] [Commented] (REEF-247) Port ranges should to be configurable for listening

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

Markus Weimer commented on REEF-247:
------------------------------------

One idea: We could introduce a new interface {{PortProvider}} to Wake:

{code}
interface PortProvider{
  int findAvailableUDPPort();
  int findAvailableTCPPort();
}
{code}

We could then use an instance of that interface wherever we need to pick ports (Wake and HTTP, for the most part). The default implementation of this interface could be {{RangePortProvider}} with two named parameters to indicate the lowest port to try and the range. Those parameters would have defaults mirroring the current setup. {{DriverConfiguration}} would get two more {{OptionalParameter}}s for this, and we'd need to make sure that those get copied into the Evaluator configuration as well.

[~bgchun], can you comment on this? 

> Port ranges should to be configurable for listening 
> ----------------------------------------------------
>
>                 Key: REEF-247
>                 URL: https://issues.apache.org/jira/browse/REEF-247
>             Project: REEF
>          Issue Type: Bug
>          Components: Wake
>    Affects Versions: 0.11
>            Reporter: Beysim Sezgin
>             Fix For: 0.11
>
>
> Many clusters restrict the IP port range that can be listened. We should have a way to configure the port range to listen on.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)