[
https://issues.apache.org/jira/browse/YARN-6486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16009615#comment-16009615
]
Carlo Curino commented on YARN-6486:
------------------------------------
I agree that if this implementation is simply pretending to see many HBs to
trigger the rest of the logic, there are more scalable ways to go about it.
[~asuresh] it seems that the kind of ideas you have been working on are being
referred to as "Global scheduling" in this context (i.e., non-HB based decision
making). Given some prod experience we have, it seems that time-based locality
also helps opening up alternative optimization strategies, so I am all for
that. As it stands I don't have anything against deprecating this, [~asuresh]
please look at the code, and see whether you think some of it should be saved
for the purposes you have in mind.
> FairScheduler: Deprecate continuous scheduling in 2.9
> -----------------------------------------------------
>
> Key: YARN-6486
> URL: https://issues.apache.org/jira/browse/YARN-6486
> Project: Hadoop YARN
> Issue Type: Task
> Components: fairscheduler
> Affects Versions: 2.9.0
> Reporter: Wilfred Spiegelenburg
> Assignee: Wilfred Spiegelenburg
>
> Mark continuous scheduling as deprecated in 2.9 and remove the code in 3.0.
> Removing continuous scheduling from the code will be logged as a separate jira
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
