You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Sunil G (JIRA)" <ji...@apache.org> on 2016/06/16 18:09:05 UTC

[jira] [Commented] (YARN-5263) Fix AMRMClientAsync AbstractCallbackHandler to notify clients of Pre-emption messages

    [ https://issues.apache.org/jira/browse/YARN-5263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15334344#comment-15334344 ] 

Sunil G commented on YARN-5263:
-------------------------------

Hi [~asuresh]
Thanks for filing the ticket.

I have some doubts. Currently scheduler sends preempted container details (message) to AM via heartbeat. And I could see that we update preemption details into PreemptionMessage as StrictContract and normal contract.
Any specific advantages for clients to know about such message. Because AM can take some action based on its loaded for preemption policy such as check point etc. May be I am missing something, pls help me to share some more information.

> Fix AMRMClientAsync AbstractCallbackHandler to notify clients of Pre-emption messages
> -------------------------------------------------------------------------------------
>
>                 Key: YARN-5263
>                 URL: https://issues.apache.org/jira/browse/YARN-5263
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Arun Suresh
>            Assignee: Arun Suresh
>
> This JIRA proposes to add a callback method to AMRMClientAsync::AbstractCallbackHandler that notifies the client AM of Pre-emption messages sent to it by the Scheduler.



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

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