You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@reef.apache.org by "Julia (JIRA)" <ji...@apache.org> on 2014/11/25 22:44:13 UTC

[jira] [Assigned] (REEF-53) Introduce NameServer interface and add default Name Server implementation

     [ https://issues.apache.org/jira/browse/REEF-53?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Julia reassigned REEF-53:
-------------------------

    Assignee: Julia

> Introduce NameServer interface and add default Name Server implementation
> -------------------------------------------------------------------------
>
>                 Key: REEF-53
>                 URL: https://issues.apache.org/jira/browse/REEF-53
>             Project: REEF
>          Issue Type: Improvement
>            Reporter: Julia
>            Assignee: Julia
>
> Currently NameServer by default is used in Bridge JobDriver and starts to run when it is constructed. If clients don’t bind any implementation, by default they will still get Name Server. 
> We would like to provide an option for clients to choose not to have NameServer if they don’t need it for performance consideration for example. 
> For that we need to 
> 1. Create an interface for NameServer
> 2. Provide DefaultNameServerImpl which implements NameServer interface but does nothing. 
> 3. Change the current NameServer to NameServerImpl to implement NameServer interface
> By this way, if the client doesn’t merge NameServer in the driver configuration, the default behavior would be no Name Server running in the JobDriver. If the client chooses to plug in the NameServer configuration, then NameServerImpl will be bound and used.  



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