[
https://issues.apache.org/jira/browse/YARN-4761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15179171#comment-15179171
]
Rohith Sharma K S commented on YARN-4761:
-----------------------------------------
I think we can move the test to TestAbstractYarnScheduler to test this JIRA
behavior. TestAbstractYarnScheduler test class extends
ParameterizedSchedulerTestBase that runs for both CS and FS.
Some test cases are specific to CS behavior are EITHER skipped for
FairScheduler OR being added in specific FairScheduler package. The test cases
which assumes CS as default scheduler need to re-visit for fairscheduer
functionality impacts like this JIRA.
> NMs reconnecting with changed capabilities can lead to wrong cluster resource
> calculations on fair scheduler
> ------------------------------------------------------------------------------------------------------------
>
> Key: YARN-4761
> URL: https://issues.apache.org/jira/browse/YARN-4761
> Project: Hadoop YARN
> Issue Type: Bug
> Components: fairscheduler
> Affects Versions: 2.6.4
> Reporter: Sangjin Lee
> Assignee: Sangjin Lee
> Attachments: YARN-4761.01.patch
>
>
> YARN-3802 uncovered an issue with the scheduler where the resource
> calculation can be incorrect due to async event handling. It was subsequently
> fixed by YARN-4344, but it was never fixed for the fair scheduler.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
