[
https://issues.apache.org/jira/browse/YARN-5611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15490929#comment-15490929
]
Sunil G commented on YARN-5611:
-------------------------------
Yes..
Adding few more thoughts:
- It makes sense to have this class for dynamic/runtime updates. So if we want
to change the priority/timeout of an app, then a common
{{ApplicationAttributes}} class can address all such common app related
attributes.
- However during submission time, its better to have these api's separately for
priority/timeout. WE use existing {{setPriority}} api to achieve this, and
hence its better to have these apis separately in AppSubmissionContext.
- For REST api, we have {{updateApplicationPriority}} to set priority of an
app. Thinking out loud, it will be easier for clients to have separate REST api
for priority or timeout. So I think we can discuss and confirm about REST side
changes.
Thoughts.?
> Provide an API to update lifetime of an application.
> ----------------------------------------------------
>
> Key: YARN-5611
> URL: https://issues.apache.org/jira/browse/YARN-5611
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: resourcemanager
> Reporter: Rohith Sharma K S
> Assignee: Rohith Sharma K S
> Attachments: YARN-5611.v0.patch
>
>
> YARN-4205 monitors an Lifetime of an applications is monitored if required.
> Add an client api to update lifetime of an application.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
