[ https://issues.apache.org/jira/browse/YARN-2022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sunil G updated YARN-2022: -------------------------- Attachment: YARN-2022.9.patch Thank you [~vinodkv] for the comments. bq.The other option that we may do is to skip the config completely and hard-code the skipping. Yes. I also feel we can hardcode for now. bq.RMContainer usually is a read only interface. setMasterContainer() doesn't belong here, please move it to RMContainerImpl. I moved setMasterContainer to RMContainerImpl. In this case, if I need to invoke setMasterContainer then I may need to raise an Event to RMContainerImpl (downcast may not be good). Please suggest your opinion. I also fixed other comments. Kindly review the updated patch. > Preempting an Application Master container can be kept as least priority when > multiple applications are marked for preemption by > ProportionalCapacityPreemptionPolicy > --------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: YARN-2022 > URL: https://issues.apache.org/jira/browse/YARN-2022 > Project: Hadoop YARN > Issue Type: Sub-task > Components: resourcemanager > Affects Versions: 2.4.0 > Reporter: Sunil G > Assignee: Sunil G > Attachments: YARN-2022-DesignDraft.docx, YARN-2022.2.patch, > YARN-2022.3.patch, YARN-2022.4.patch, YARN-2022.5.patch, YARN-2022.6.patch, > YARN-2022.7.patch, YARN-2022.8.patch, YARN-2022.9.patch, Yarn-2022.1.patch > > > Cluster Size = 16GB [2NM's] > Queue A Capacity = 50% > Queue B Capacity = 50% > Consider there are 3 applications running in Queue A which has taken the full > cluster capacity. > J1 = 2GB AM + 1GB * 4 Maps > J2 = 2GB AM + 1GB * 4 Maps > J3 = 2GB AM + 1GB * 2 Maps > Another Job J4 is submitted in Queue B [J4 needs a 2GB AM + 1GB * 2 Maps ]. > Currently in this scenario, Jobs J3 will get killed including its AM. > It is better if AM can be given least priority among multiple applications. > In this same scenario, map tasks from J3 and J2 can be preempted. > Later when cluster is free, maps can be allocated to these Jobs. -- This message was sent by Atlassian JIRA (v6.2#6252)