[ 
https://issues.apache.org/jira/browse/YARN-5221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arun Suresh updated YARN-5221:
------------------------------
    Attachment: YARN-5221.011.patch

Updating patch based on [~subru]'s and [~leftnoteasy]'s suggestions.

bq. Not sure if the change will cause stored data compability issues while 
doing rolling upgrade. (New NM read old data)
So new NM will be able to read old data.. but not the other way around.

bq. Lots of unnecessary formatting changes, is it possible to revert these 
changes?
Actually many of the formatting changes are due to fixing the existing code to 
the correct code-style :) If you dont mind, can we keep this as it is, since 
rolling that back to the wrong code style is a bit difficult...

> Expose UpdateResourceRequest API to allow AM to request for change in 
> container properties
> ------------------------------------------------------------------------------------------
>
>                 Key: YARN-5221
>                 URL: https://issues.apache.org/jira/browse/YARN-5221
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Arun Suresh
>            Assignee: Arun Suresh
>         Attachments: YARN-5221.001.patch, YARN-5221.002.patch, 
> YARN-5221.003.patch, YARN-5221.004.patch, YARN-5221.005.patch, 
> YARN-5221.006.patch, YARN-5221.007.patch, YARN-5221.008.patch, 
> YARN-5221.009.patch, YARN-5221.010.patch, YARN-5221.011.patch
>
>
> YARN-1197 introduced APIs to allow an AM to request for Increase and Decrease 
> of Container Resources after initial allocation.
> YARN-5085 proposes to allow an AM to request for a change of Container 
> ExecutionType.
> This JIRA proposes to unify both of the above into an Update Container API.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to