[
https://issues.apache.org/jira/browse/YARN-6486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16005078#comment-16005078
]
Arun Suresh commented on YARN-6486:
-----------------------------------
Any reason why you would want to deprecate this ?
Think we should unify Async Scheduling (from the Capacity Scheduler) and
Continuous scheduling, since it looks pretty similar. Atleast the triggering
thread can be made a common RM service.
There are some interesting scheduling performance improvements that can be done
using a non-HB driven approach, coupled with time-based localilty relaxation
that I've been experimenting with, both of which are offered by the Fair
Scheduler. it would be sad to see this deprecated as a feature.
Thoughts ? (cc: [[email protected]], [~subru], [~leftnoteasy], [~curino])
> 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]