Rohith Sharma K S commented on YARN-4014:

bq. When 2nd or subsequent AM attempt is spawned, we are never setting the old 
attempt as null in SchedulerApplication, correct? Hence there is a chance that 
we set priority to old attempt while new attempt is getting created.. 
Right.. Since latest priority has been reset to attempt after attempt got 
updated in the SchedulerApplication#setCurrentAttempt, I think there would NOT 
ocur any possibility where currentAttempt has old priority. So I believe 
currentAttempt NEED NOT to be volatile.
[~jianhe] Could you give your opinion on this?

> Support user cli interface in for Application Priority
> ------------------------------------------------------
>                 Key: YARN-4014
>                 URL: https://issues.apache.org/jira/browse/YARN-4014
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: client, resourcemanager
>            Reporter: Rohith Sharma K S
>            Assignee: Rohith Sharma K S
>         Attachments: 0001-YARN-4014-V1.patch, 0001-YARN-4014.patch, 
> 0002-YARN-4014.patch, 0003-YARN-4014.patch, 0004-YARN-4014.patch, 
> 0004-YARN-4014.patch
> Track the changes for user-RM client protocol i.e ApplicationClientProtocol 
> changes and discussions in this jira.

This message was sent by Atlassian JIRA

Reply via email to