tez-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Harish Jaiprakash (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TEZ-4028) Events not visible from proto history logging for s3a filesystem until dag completes.
Date Thu, 10 Jan 2019 06:33:00 GMT

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

Harish Jaiprakash commented on TEZ-4028:
----------------------------------------

Thanks [~ewohlstadter]. Adding a new constant and using it in both test and service. Please
take a look.

> Events not visible from proto history logging for s3a filesystem until dag completes.
> -------------------------------------------------------------------------------------
>
>                 Key: TEZ-4028
>                 URL: https://issues.apache.org/jira/browse/TEZ-4028
>             Project: Apache Tez
>          Issue Type: Bug
>            Reporter: Harish Jaiprakash
>            Assignee: Harish Jaiprakash
>            Priority: Major
>         Attachments: TEZ-4028.01.patch, TEZ-4028.02.patch
>
>
> The events are not visible in the files because  s3 filesystem
> * flush writes to local disk and only upload/commit to s3 on close.
> * does not support append
> As an initial fix we log the dag submitted, initialized and started events into a file
and these can be read to get the dag plan, config from the AM. The counters are anyways not
available until the dag completes.
> The in-progress information cannot be read, this can be obtained from the AM once we
have the above events.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message