Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Sat, 16 Jul 2016 19:31:20 +0000 (UTC)
From: "Carlo Curino (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12987337.1467848456000.50975.1468697480481@Atlassian.JIRA>
In-Reply-To: <JIRA.12987337.1467848456000@Atlassian.JIRA>
References: <JIRA.12987337.1467848456000@Atlassian.JIRA> <JIRA.12987337.1467848456275@arcas>
Subject: [jira] [Commented] (YARN-5323) Policies APIs (for Router and
 AMRMProxy policies)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Sat, 16 Jul 2016 19:31:22 -0000


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

Carlo Curino commented on YARN-5323:
------------------------------------

This initial patch presents the APIs for policies (implementations in YARN-5324, YARN-5325). The key philosophy of our design is to: 
 # have a very opaque format in the federation store, so that we can evolve policy freely (likely to happen as we experience with this).  To assist with this though, we foresee each {{FederationPolicy}} to implement the {{FederationPolicyWriter}} interface that allows us to control the entire lifecycle of a policy. The envisioned usage is: 1) a {{FederationPolicy}} is instantiated as part of the admin tools, and configure by setting all sort of configs in it (which might change drastically as policies get more sophisticated), 2) the admin tools invoke {{serialize()}} and get a {{FederationPolicyConfiguration}} out of it that is stored in the policy store, 3) on the router/amrmproxy side this is fetched, a FederationPolicy object is instantiated, and via the {{FederationPolicyConfigurator}} apis the {{RouterPolicy}} and {{AMRMProxyFederationPolicy}} are instantiated and initialized. 
 # Note that we actively want to bind together the choice of {{AMRMProxyFederationPolicy}} and {{RouterPolicy}}, which must be coordinated to operate correctly. As such the {{FederationPolicyConfigurator}} is a way to raise the bar for a misconfiguration (one needs to write a class that mistakenly combines to policies, instead of just mistyping a conf). This also allows to do consistency checks among the configurations of the two policies. 


> Policies APIs (for Router and AMRMProxy policies)
> -------------------------------------------------
>
>                 Key: YARN-5323
>                 URL: https://issues.apache.org/jira/browse/YARN-5323
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: nodemanager, resourcemanager
>            Reporter: Carlo Curino
>            Assignee: Carlo Curino
>         Attachments: YARN-5323.01.patch
>
>
> This JIRA tracks APIs for the policies that will guide the Router and AMRMProxy decisions on where to fwd the jobs submission/query requests as well as ResourceRequests.


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

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org