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 2017/07/06 02:47:00 UTC

[jira] [Comment Edited] (REEF-1820) Allow specify node names when requesting evaluators

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

Julia edited comment on REEF-1820 at 7/6/17 2:46 AM:
-----------------------------------------------------

You mean another Submit() API or another EvaluatorRequest? Currently, in REEF Java, public final class EvaluatorRequest contains List<String> nodeNames. 



was (Author: juliaw):
You mean another Submit(0 API or another public final class EvaluatorRequest? Currently, in REEF Java, public final class EvaluatorRequest contains List<String> nodeNames. 


> Allow specify node names when requesting evaluators
> ---------------------------------------------------
>
>                 Key: REEF-1820
>                 URL: https://issues.apache.org/jira/browse/REEF-1820
>             Project: REEF
>          Issue Type: Task
>          Components: REEF, REEF Bridge
>            Reporter: Julia
>            Priority: Minor
>
> Currently, when clients request for evaluators, .Net REEF doesn't not expose node names in IEvaluatorRequest. It default to null node names therefore it is up to YARN to assign available containers. 
> Some of the REEF clients would like to specify node names when requesting for evaluators. We should allow the preferred node names to be specified through IEvaluatorRequest and pass it to Java EvaluatorRequestorBridge. 
> As resources requested may not be available for various reasons, we should also allow the client to specify RelaxLocality in the IEvaluatorRequest. Setting RelaxLocality to true would allow YARN to return another container if the specified one is not available. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)