[
https://issues.apache.org/jira/browse/YARN-2575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15134578#comment-15134578
]
Sean Po commented on YARN-2575:
-------------------------------
YARN-2575.v8.patch fixes a javadoc error that resulted from a typo in a
javadoc.
The remaining javadoc errors are caused by the use of '_' as an identifier
which might not be supported in the future. They are not related to my changes.
The checkstyle issues already existed in the past:
Too many parameters: AllocationConfiguration.java:108: public
AllocationConfiguration(Map<String, Resource> minQueueResources,:10: More than
7 parameters (found 22).
Method too long: AllocationFileLoaderService.java:205: public synchronized
void reloadAllocations() throws IOException,:3: Method length is 216 lines (max
allowed is 150).
Too many parameters: AllocationFileLoaderService.java:427: private void
loadQueue(String parentName, Element element,:16: More than 7 parameters (found
17).
The test failures hadoop.yarn.server.resourcemanager.TestClientRMTokens and
hadoop.yarn.server.resourcemanager.TestAMAuthorization are known failures and
are covered in HADOOP-12687.
> Consider creating separate ACLs for Reservation create/update/delete/list ops
> -----------------------------------------------------------------------------
>
> Key: YARN-2575
> URL: https://issues.apache.org/jira/browse/YARN-2575
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: capacityscheduler, fairscheduler, resourcemanager
> Reporter: Subru Krishnan
> Assignee: Sean Po
> Attachments: YARN-2575.v1.patch, YARN-2575.v2.1.patch,
> YARN-2575.v2.patch, YARN-2575.v3.patch, YARN-2575.v4.patch,
> YARN-2575.v5.patch, YARN-2575.v6.patch, YARN-2575.v7.patch, YARN-2575.v8.patch
>
>
> YARN-1051 introduces the ReservationSystem and in the current implementation
> anyone who can submit applications can also submit reservations. This JIRA is
> to evaluate creating separate ACLs for Reservation create/update/delete ops.
> Depends on YARN-4340
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
