[
https://issues.apache.org/jira/browse/YARN-1702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Varun Vasudev updated YARN-1702:
--------------------------------
Attachment: apache-yarn-1702.13.patch
{quote}
We now have double Audit logs in some cases
{quote}
Removed the extra log call.
{quote}
RMWebServices is doing an extra hasAccess check that is unnecessary.
For the updateState API, should we just send the latest AppState instead of
AppInfo? If we do this, we should also change tests to validate the app-state
besides HttpStatus.
{quote}
Fixed both. Added check in the tests to confirm app state via rmcontext.
{quote}
Test shouldn't explicitly depend on CS
{quote}
The root queue by default allows anyone queue admin status which means we can't
test kill permissions. Ideally, we should fix that in CapacityScheduler but for
now I thought this was the best workaround.
> Expose kill app functionality as part of RM web services
> --------------------------------------------------------
>
> Key: YARN-1702
> URL: https://issues.apache.org/jira/browse/YARN-1702
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Varun Vasudev
> Assignee: Varun Vasudev
> Attachments: apache-yarn-1702.10.patch, apache-yarn-1702.11.patch,
> apache-yarn-1702.12.patch, apache-yarn-1702.13.patch,
> apache-yarn-1702.2.patch, apache-yarn-1702.3.patch, apache-yarn-1702.4.patch,
> apache-yarn-1702.5.patch, apache-yarn-1702.7.patch, apache-yarn-1702.8.patch,
> apache-yarn-1702.9.patch
>
>
> Expose functionality to kill an app via the ResourceManager web services API.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
