[
https://issues.apache.org/jira/browse/YARN-6486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wilfred Spiegelenburg updated YARN-6486:
----------------------------------------
Attachment: YARN-6486.001.patch
Patch marking all continuous scheduling public methods deprecated.
There is no documentation for continuous scheduling or its settings so no
documentation updates. Since there is no code change there are no new tests
added.
The FairScheduler is marked @ LimitedPrivate("yarn") @ Unstable and
FairSchedulerConfig is marked as @ Private @ Evolving. Based on the
compatibility guidelines we should be able to remove the code in a later hadoop
3.x release.
Since we might have clusters using this we should allow enough time for users
to reconfigure clusters and move away from continuous scheduling.
> FairScheduler: Deprecate continuous scheduling
> ----------------------------------------------
>
> 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
> Attachments: YARN-6486.001.patch
>
>
> 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.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
