tez-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hitesh Shah (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TEZ-2035) Make timeline server putDomain exceptions non-fatal
Date Thu, 05 Feb 2015 00:08:35 GMT

    [ https://issues.apache.org/jira/browse/TEZ-2035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14306267#comment-14306267
] 

Hitesh Shah commented on TEZ-2035:
----------------------------------

bq. There is likely another follow-on effort that could disable timeline server operations
for the AM if putDomain fails.
I am assuming this will hold true only for cases where ACLs are being enforced? 

+1 for the change for now. However, from a security point of view, the above follow up should
be considered a blocker for 0.6.1 to ensure that data is not exposed in case a putDomain fails
for some reason.  


 

> Make timeline server putDomain exceptions non-fatal
> ---------------------------------------------------
>
>                 Key: TEZ-2035
>                 URL: https://issues.apache.org/jira/browse/TEZ-2035
>             Project: Apache Tez
>          Issue Type: Improvement
>            Reporter: Jonathan Eagles
>            Assignee: Jonathan Eagles
>         Attachments: TEZ-2035.1.patch
>
>
> Timeline server operations have been non-fatal. However, the put domain operation is
fatal and will cause the job to fail to submit. This patch is a simple fix to make the exception
non-fatal. There is likely another follow-on effort that could disable timeline server operations
for the AM if putDomain fails.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message