[
https://issues.apache.org/jira/browse/YARN-7018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16595575#comment-16595575
]
Wangda Tan commented on YARN-7018:
----------------------------------
[~jlowe], given the fields need to be updated should all inside scheduler (Such
as SchedulerNode#unallocatedResource). For this purpose, is it better to just
add a plugin to scheduler instead of to RMActiveService? The plugin itself
could be scheduler agnostic (just like AppPlacementAllocator), and to use these
plugins, changing a little bit scheduler code seems fine. Adding to
RMActiveService is additional cost to maintenance, we have to consider
scheduler reinitialize (if it is stateful) and other scheduler related
interactions.
Just my $.02
> 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
>
>
> 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
