hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Subru Krishnan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-7124) CLONE - Log aggregation deletes/renames while file is open
Date Mon, 09 Oct 2017 20:58:05 GMT

    [ https://issues.apache.org/jira/browse/YARN-7124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16197684#comment-16197684

Subru Krishnan commented on YARN-7124:

[~jlowe], [~daryn], [~djp], do you guys have a port for YARN-7083 for trunk/branch-2 as this
is a blocker for 2.9.0 release? Thanks!

> CLONE - Log aggregation deletes/renames while file is open
> ----------------------------------------------------------
>                 Key: YARN-7124
>                 URL: https://issues.apache.org/jira/browse/YARN-7124
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: nodemanager
>    Affects Versions: 2.8.2
>            Reporter: Daryn Sharp
>            Priority: Critical
> YARN-6288 changes the log aggregation writer to be an autoclosable.  Unfortunately the
try-with-resources block for the writer will either rename or delete the log while open.
> Assuming the NM's behavior is correct, deleting open files only results in ominous WARNs
in the nodemanager log and increases the rate of logging in the NN when the implicit try-with-resource
close fails.  These red herrings complicate debugging efforts.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org

View raw message