hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Lowe (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-7083) Log aggregation deletes/renames while file is open
Date Mon, 28 Aug 2017 22:01:05 GMT

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

Jason Lowe commented on YARN-7083:

I'm OK with fixing in 2.8.x and filing a followup JIRA.  If that followup isn't going to be
fixed for a bit it may make more sense to revert YARN-6876 until it's ready to address the
issue to avoid shipping this bug in 3.0.0-beta1 or 2.9.0.

> Log aggregation deletes/renames while file is open
> --------------------------------------------------
>                 Key: YARN-7083
>                 URL: https://issues.apache.org/jira/browse/YARN-7083
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: nodemanager
>    Affects Versions: 2.8.2
>            Reporter: Daryn Sharp
>            Assignee: Jason Lowe
>            Priority: Critical
>         Attachments: YARN-7083.001.patch
> 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