Sunil G commented on YARN-4170:

Thanks [~jianhe]
Yes. For simplicity, its definitely a better option. Also thinking for options 
other than *map*, I could pull the change priority info from RMAppAttempt. But 
this also will need a variable (a boolean perhaps) to store last changed 
priority info per attempt level. It will have two states and when a priority 
change request is done at scheduler, this boolean can be turned ON. Thus by 
seeing this, AM can be updated with changed priority. Yes, its more like 
keeping a state change, still a possible option, how do u feel about this.

> AM need to be notified with priority in AllocateResponse 
> ---------------------------------------------------------
>                 Key: YARN-4170
>                 URL: https://issues.apache.org/jira/browse/YARN-4170
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: resourcemanager
>            Reporter: Sunil G
>            Assignee: Sunil G
>         Attachments: 0001-YARN-4170.patch, 0002-YARN-4170.patch, 
> 0003-YARN-4170.patch, 0004-YARN-4170.patch, 0005-YARN-4170-v2.patch
> As discussed in MAPREDUCE-5870, Application Master need to be notified with 
> priority in Allocate heartbeat.  This will help AM to know the priority and 
> can update JobStatus when client asks. 

This message was sent by Atlassian JIRA

Reply via email to