[
https://issues.apache.org/jira/browse/TEZ-3404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15440520#comment-15440520
]
Harish Jaiprakash commented on TEZ-3404:
----------------------------------------
DagAppMaster submits AMLaunchedEvent even before historyService has been
started (during the init phase itself). Current code works in that case too
(couple of test cases failed, because I assumed that this should not be
happening), but just wanted to know if its acceptable to do this?
In session mode, should dag domain id be created even when there are no dag
acls? I think I have regressed on this, right now I've changed the test case.
But if its not ok, I'll revert to the older behaviour.
> Remove blocking call for ATS domain creation from client side to AM
> -------------------------------------------------------------------
>
> Key: TEZ-3404
> URL: https://issues.apache.org/jira/browse/TEZ-3404
> Project: Apache Tez
> Issue Type: Improvement
> Reporter: Harish Jaiprakash
> Assignee: Harish Jaiprakash
> Attachments: TEZ-3404-WIP-01.patch, TEZ-3404-WIP-02.patch,
> TEZ-3404-WIP-03.patch, TEZ-3404-WIP-04.patch, TEZ-3404-WIP-05.patch
>
>
> Today, there is a blocking call for creating the domain on the client side
> which blocks hive query throughput. We need to move this to the AM and still
> retain the same security guarantees.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
