[
https://issues.apache.org/jira/browse/YARN-998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15215690#comment-15215690
]
Brahma Reddy Battula commented on YARN-998:
-------------------------------------------
Following test fails in trunk...Even jenkin report(pre-commit) of this issue
shows this was failing..
{noformat}
Running org.apache.hadoop.yarn.server.resourcemanager.TestRMAdminService
Tests run: 23, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 16.363 sec <<<
FAILURE! - in org.apache.hadoop.yarn.server.resourcemanager.TestRMAdminService
testResourcePersistentForNMRegistrationWithNewResource(org.apache.hadoop.yarn.server.resourcemanager.TestRMAdminService)
Time elapsed: 0.616 sec <<< FAILURE!
org.junit.ComparisonFailure: expected:<<memory:[8192, vCores:8]>> but
was:<<memory:[4096, vCores:4]>>
at org.junit.Assert.assertEquals(Assert.java:115)
at org.junit.Assert.assertEquals(Assert.java:144)
at
org.apache.hadoop.yarn.server.resourcemanager.TestRMAdminService.testResourcePersistentForNMRegistrationWithNewResource(TestRMAdminService.java:310)
{noformat}
> Keep NM resource updated through dynamic resource config for RM/NM restart
> --------------------------------------------------------------------------
>
> Key: YARN-998
> URL: https://issues.apache.org/jira/browse/YARN-998
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: graceful, nodemanager, scheduler
> Reporter: Junping Du
> Assignee: Junping Du
> Fix For: 2.8.0
>
> Attachments: YARN-998-sample.patch, YARN-998-v1.patch,
> YARN-998-v2.1.patch, YARN-998-v2.patch, YARN-998-v3.patch
>
>
> When NM is restarted by plan or from a failure, previous dynamic resource
> setting should be kept for consistency.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
