[
https://issues.apache.org/jira/browse/YARN-8898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16685683#comment-16685683
]
Bibin A Chundatt commented on YARN-8898:
----------------------------------------
{quote}
In FederationStateStore there's already an application table, we can piggyback
in it (ApplicationHomeSubCluster).
{quote}
Initially , i was thinking of adding to ApplicationHomeSubCluster.
As per the current implementation subcluster Id is written to znode not
ApplicationHomeSubCluster to bytes.
Upgrade from 3 to 3.3 scenario will be an issue in this case rt. No store
version too for now.
Rolling upgrade might not be possible if new table is not added. Hope my
analysis is correct.
{quote}
If by trimming you meant setting some of the entries to null, then sure by all
means.
{quote}
Yes meant .Setting to null not new proto :)
Following was what i had in my mind.
{noformat}
* |--- MEMBERSHIP
* | |----- SC1
* | |----- SC2
* |--- APPLICATION
* | |----- APP1
* | |----- APP2
* |--- POLICY
* | |----- QUEUE1
* | |----- QUEUE1
* |--- APPLICATIONDATA
* |----- APP1
* |----- APP2
{noformat}
{code}
public interface FederationStateStore
extends FederationApplicationHomeSubClusterStore,
FederationMembershipStateStore, FederationPolicyStore,
FederationApplicationDataStore
{code}
> Fix FederationInterceptor#allocate to set application priority in
> allocateResponse
> ----------------------------------------------------------------------------------
>
> Key: YARN-8898
> URL: https://issues.apache.org/jira/browse/YARN-8898
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Bibin A Chundatt
> Assignee: Bilwa S T
> Priority: Major
> Attachments: YARN-8898.wip.patch
>
>
> In case of FederationInterceptor#mergeAllocateResponses skips
> application_priority in response returned
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
