[
https://issues.apache.org/jira/browse/YARN-7390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16219625#comment-16219625
]
Haibo Chen commented on YARN-7390:
----------------------------------
Like Yufei said, we have considered parameterizing all unit tests that are
supposed to be scheduler agonistic vs just removing code based on the
assumption of CapacityScheduler. The latter is necessary in either case. The
con of the former option is much increased unit test turnout time which may
raise concerns in the community, whereas the latter allows us internally to run
all unit tests against Fair Scheduler with a simple change of default
scheduler. Not sure if we need to have some discussion in the community if we
were to parameterize all scheduler-agnostic tests. Thoughts?
> All reservation related test cases failed when TestYarnClient runs against
> Fair Scheduler.
> ------------------------------------------------------------------------------------------
>
> Key: YARN-7390
> URL: https://issues.apache.org/jira/browse/YARN-7390
> Project: Hadoop YARN
> Issue Type: Bug
> Components: fairscheduler, reservation system
> Affects Versions: 2.9.0, 3.0.0, 3.1.0
> Reporter: Yufei Gu
> Assignee: Yufei Gu
> Attachments: YARN-7390.001.patch
>
>
> All reservation related test cases failed when {{TestYarnClient}} runs
> against Fair Scheduler. To reproduce it, you need to set scheduler class to
> Fair Scheduler in yarn-default.xml.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
