[jira] [Commented] (TEZ-3366) Tez timeline client reporting different domains for same entity

["Hitesh Shah (JIRA)" <ji...@apache.org>]

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

Hitesh Shah commented on TEZ-3366:
----------------------------------

FWIW, it seems like you have tez acls enabled which will end up trying to create domains. This could be disabled if you do not really have a secure cluster as the acls can easily be circumvented by simply making calls with a "?user.name=" appended to the timeline webservice call. This has been fixed via TEZ-3177. 

> Tez timeline client reporting different domains for same entity
> ---------------------------------------------------------------
>
>                 Key: TEZ-3366
>                 URL: https://issues.apache.org/jira/browse/TEZ-3366
>             Project: Apache Tez
>          Issue Type: Bug
>         Environment: centos 6.6
> apache hadoop 2.6.4
> tez 0.6.2
>            Reporter: Nikhil Mulley
>
> Hi,
> Timeline server service logs on 2.6.4 cluster (no security, no acls) show often these error and then an exception follows when tez job runs. Closely inspecting the code shows there is a possibility of tez itself reporting different domain for the same entity (one that is already also in the timeline store) and then getting skipped to handle the event and store the event timeline information. 
> >>>>
> ERROR org.apache.hadoop.yarn.server.timeline.TimelineDataManager: Skip the timeline entity: { id: tez_container_1468970783049_0021_01_000002, type: TEZ_CONTAINER_ID }
> >>>
> >>>
> org.apache.hadoop.yarn.exceptions.YarnException: The domain of the timeline entity { id: tez_container_1468970783049_0021_01_000002, type: TEZ_CONTAINER_ID } is not allowed to be changed.
> >>>



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