You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@tez.apache.org by "Hitesh Shah (JIRA)" <ji...@apache.org> on 2016/03/31 20:32:25 UTC

[jira] [Updated] (TEZ-3177) Non-DAG events should use the session domain or no domain if the data does not need protection

     [ https://issues.apache.org/jira/browse/TEZ-3177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hitesh Shah updated TEZ-3177:
-----------------------------
    Attachment: TEZ-3177.1.patch

Made AM/Container events use sessionDomainId always. Also minor fix to use dag counter for domainIds as dag names are not unique. 

> Non-DAG events should use the session domain or no domain if the data does not need protection 
> -----------------------------------------------------------------------------------------------
>
>                 Key: TEZ-3177
>                 URL: https://issues.apache.org/jira/browse/TEZ-3177
>             Project: Apache Tez
>          Issue Type: Bug
>            Reporter: Hitesh Shah
>            Assignee: Hitesh Shah
>         Attachments: TEZ-3177.1.patch
>
>
> There have been issues noticed where when using dag specific domains, container events get generated under different dags causing issues as they are updated using different domains. 



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