[ https://issues.apache.org/jira/browse/YARN-3866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15796464#comment-15796464 ]
Junping Du edited comment on YARN-3866 at 1/3/17 10:54 PM: ----------------------------------------------------------- The unit tests failed shouldn't be relevant to the patch. Most failed tests are common seen, the only one I didn't noticed before is TestCapacitySchedulerSurgicalPreemption which get tracked in YARN-5973. I verified locally to see if w/o the patch will affect these unit test failures. Here is the results: | Tests | Without Patch | With Patch | | TestCapacitySchedulerSurgicalPreemption | FAILED | FAILED | | TestAMAuthorization | FAILED | FAILED | | TestFairScheduler | SUCCEED | SUCCEED | | TestClientRMTokens | FAILED | FAILED | | TestAMRMProxy | SUCCEED | SUCCEED | | TestGetGroups | FAILED | FAILED | >From JACC report, we can see previous incompatible API issues involved in >YARN-3866 are resolved. The javac warning is just annoying because we are >adding back deprecated APIs for better compatibility. I am planning to go ahead to commit the latest addendum patch before the end of today. Please comments if you have any concerns. was (Author: djp): The unit tests failed shouldn't be relevant to the patch. Most failed tests are common seen, the only one I didn't noticed before is TestCapacitySchedulerSurgicalPreemption which get tracked in YARN-5973. I verified locally to see if w/o the patch will affect these unit test failures. Here is the results: | Tests | Without Patch | With Patch | | ----------------------------------------- |:-------------:| -----------:| | TestCapacitySchedulerSurgicalPreemption | FAILED | FAILED | | TestAMAuthorization | FAILED | FAILED | | TestFairScheduler | SUCCEED | SUCCEED | | TestClientRMTokens | FAILED | FAILED | | TestAMRMProxy | SUCCEED | SUCCEED | | TestGetGroups | FAILED | FAILED | >From JACC report, we can see previous incompatible API issues involved in >YARN-3866 are resolved. The javac warning is just annoying because we are >adding back deprecated APIs for better compatibility. I am planning to go ahead to commit the latest addendum patch before the end of today. Please comments if you have any concerns. > AM-RM protocol changes to support container resizing > ---------------------------------------------------- > > Key: YARN-3866 > URL: https://issues.apache.org/jira/browse/YARN-3866 > Project: Hadoop YARN > Issue Type: Sub-task > Components: api > Reporter: MENG DING > Assignee: MENG DING > Priority: Blocker > Fix For: 2.8.0, 3.0.0-alpha1 > > Attachments: YARN-3866-YARN-1197.4.patch, > YARN-3866-branch-2.8.addendum.1.patch, YARN-3866-branch-2.8.addendum.1.patch, > YARN-3866-branch-2.8.addendum.2.patch, YARN-3866-branch-2.8.addendum.3.patch, > YARN-3866.1.patch, YARN-3866.2.patch, YARN-3866.3.patch > > > YARN-1447 and YARN-1448 are outdated. > This ticket deals with AM-RM Protocol changes to support container resize > according to the latest design in YARN-1197. > 1) Add increase/decrease requests in AllocateRequest > 2) Get approved increase/decrease requests from RM in AllocateResponse > 3) Add relevant test cases -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org