[
https://issues.apache.org/jira/browse/YARN-5611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15593578#comment-15593578
]
Vinod Kumar Vavilapalli commented on YARN-5611:
-----------------------------------------------
HADOOP-11552 may be an easy out as long as we agree it makes into the next
release where app-timeouts feature and update-priorities exists. Otherwise, we
risk regressing on high-availability. Let's make sure this is a blocker.
OTOH, even assuming HADOOP-11552, there is one API concern I have. If multiple
users start trying to update the timeout for a single application, the behavior
from individual user's point of view is arbitrary. Both the user's clients
block, and after the call returns, the timeout may be set to the value that
they asked for or what the other user asked for.
To avoid this, the API should be something like {{targetTimeoutFromNow(long
abSoluteTimeoutValueAtRequest, targetTimeout)}} so that the server can reject
requests if the current recorded value changes by the time the request is
accepted. Essentially this is {{Read -> CompareAndSetOrFail}}.
> 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: 0001-YARN-5611.patch, 0002-YARN-5611.patch,
> 0003-YARN-5611.patch, 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]
