[jira] [Issue Comment Deleted] (YARN-7018) Interface for adding extra behavior to node heartbeats

["Manikandan R (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/YARN-7018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Manikandan R updated YARN-7018:
-------------------------------
    Comment: was deleted

(was: [~jlowe] Thanks for detailed comments.

{quote}That's why it may be important to either pass the RMContext to the plugin when it is called or at least pass the context when the plugin is instantiated.{quote}

Taken care. I think we may require RMNode argument as well as it is the only arg being passed to nodeUpdate() method. Can we start moving possible methods from scheduler class to this plugin impl?

{quote}The plugin should not be loaded on every heartbeat. The plugin needs to be loaded when the RM initializes. Bonus points if we support re-initializing it when a scheduler config refresh occurs (e.g.: refreshQueues command from admin CLI). {quote}

Taken care. Plugin object would be loaded only once during RM initialization and has been kept inside RMContext for future references. Since RMContext has plugin object, when a scheduler config refresh occurs, loading the plugin object again and storing it in 
)

> 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
>
>
> 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-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org