[
https://issues.apache.org/jira/browse/YARN-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14629394#comment-14629394
]
Arun Suresh commented on YARN-3535:
-----------------------------------
bq. I think recoverResourceRequest will not be affected by whether container
finished event is processed faster. Cause recoverResourceRequest only process
the ResourceRequest in container and not care its status.
I agree with [~peng.zhang] here. IIUC, The {{recoverResourceRequest}} only
affects state of the Scheduler and the SchedulerApp. In any case, the fact that
the container is killed (the outcome of the
{{RMAppAttemptContainerFinishedEvent}} fired by
{{FinishedTransition#transition}}) will be notified to the Scheduler.. and that
notification will happen only AFTER the recoverResourceRequest has completed..
since it will be handled by the same dispatcher.
> ResourceRequest should be restored back to scheduler when RMContainer is
> killed at ALLOCATED
> ---------------------------------------------------------------------------------------------
>
> Key: YARN-3535
> URL: https://issues.apache.org/jira/browse/YARN-3535
> Project: Hadoop YARN
> Issue Type: Bug
> Affects Versions: 2.6.0
> Reporter: Peng Zhang
> Assignee: Peng Zhang
> Priority: Critical
> Attachments: 0003-YARN-3535.patch, 0004-YARN-3535.patch,
> 0005-YARN-3535.patch, YARN-3535-001.patch, YARN-3535-002.patch, syslog.tgz,
> yarn-app.log
>
>
> During rolling update of NM, AM start of container on NM failed.
> And then job hang there.
> Attach AM logs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
