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

Manikandan R edited comment on YARN-7018 at 12/3/18 5:28 PM:
-------------------------------------------------------------

{quote}Since the plugin has init and stop, wondering if we should just have the 
plugin extend Service so we have the full init/start/stop 
lifecycle.{quote}Makes sense. Incorporated the same in attached patch.
Also fixed typo issue.

[~leftnoteasy] Can you please take a look?


was (Author: maniraj...@gmail.com):
 \{quote}Since the plugin has init and stop, wondering if we should just have 
the plugin extend Service so we have the full init/start/stop lifecycle.\{quote}

Makes sense. Incorporated the same in attached patch.

Also fixed typo issue.

[~leftnoteasy] Can you please take a look?

> Interface for adding extra behavior to node heartbeats
> ------------------------------------------------------
>
>                 Key: YARN-7018
>                 URL: https://issues.apache.org/jira/browse/YARN-7018
>             Project: Hadoop YARN
>          Issue Type: New Feature
>          Components: resourcemanager
>            Reporter: Jason Lowe
>            Assignee: Jason Lowe
>            Priority: Major
>         Attachments: YARN-7018.POC.001.patch, YARN-7018.POC.002.patch, 
> YARN-7018.POC.003.patch, YARN-7018.POC.004.patch
>
>
> This JIRA tracks an interface for plugging in new behavior to node heartbeat 
> processing.  Adding a formal interface for additional node heartbeat 
> processing would allow admins to configure new functionality that is 
> scheduler-independent without needing to replace the entire scheduler.  For 
> example, both YARN-5202 and YARN-5215 had approaches where node heartbeat 
> processing was extended to implement new functionality that was essentially 
> scheduler-independent and could be implemented as a plugin with this 
> interface.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
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