Rohith Sharma K S commented on YARN-5611:

bq. I'm thinking whether makes sense to have a single API which incorporates 
these updates. That way, we don't need to add new API method again and again.
I had offline discussion with [~vvasudev] for having single API which 
incorporates application updates. But one of the point of concern when doing 
multiple applications entities update, What is the return status for users when 
any one of the entity update fails? Say, consider that as of now priority and 
timeout can be clubbed into ApplicationUpdates which can be used in future. The 
concern is  
# update *priority* OR *timeout* only, success/failure can be identified and 
return corresponding error codes. 
# update *priority* AND *timeout*. What is the error code sent to User when  
priority is updated successfully and timeout update fails.? This scenario 
handling would be difficult in future also as many update entities getting 

I think it would be better to go ahead with individual API updates only. 

> 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

To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org

Reply via email to