[
https://issues.apache.org/jira/browse/YARN-7612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16284825#comment-16284825
]
Arun Suresh commented on YARN-7612:
-----------------------------------
[~leftnoteasy], was looking at your comment a bit more.. missed a point:
bq. The interaction between Algorithm & PlacementProcessor is too tightly
coupled: Processor called algorithm once and get a response....
Actually, if you look at the latest patch - it is kind of de-coupled already.
In the latest patch, the processor does not communicate directly with the
algorithm. There is a class called a {{PlacementDIspatcher}} to connect the
Processor with the algorithm. The processor dispatches requests to the
dispatcher which is what actually calls the algorithm, and the results of the
Algorithm are held in the dispatcher till the processor pulls it.
> Add Placement Processor and planner framework
> ---------------------------------------------
>
> Key: YARN-7612
> URL: https://issues.apache.org/jira/browse/YARN-7612
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Arun Suresh
> Assignee: Arun Suresh
> Attachments: YARN-7612-YARN-6592.001.patch,
> YARN-7612-YARN-6592.002.patch, YARN-7612-v2.wip.patch, YARN-7612.wip.patch
>
>
> This introduces a Placement Processor and a Planning algorithm framework to
> handle placement constraints and scheduling requests from an app and places
> them on nodes.
> The actual planning algorithm(s) will be handled in a YARN-7613.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
