hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Busbey (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-6509) Add a size threshold beyond which yarn logs will require a force option
Date Mon, 24 Apr 2017 17:53:04 GMT

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

Sean Busbey commented on YARN-6509:

That's not correct. The prior released behavior is to read the entire log file. YARN-5088
added the option to limit that, but defaulted it to Long.MAX_VALUE. This now defaults the
behavior to the last ~4KiB of logs. I suppose one could argue about wether or not getting
the last Long.MAX_VALUE worth of logs instead of all of them should be considered an incompatible
change. For just about everyone I'm guessing the two conditions are equivalent. The number
of folks impacted by changing to 4KiB is much larger.

> Add a size threshold beyond which yarn logs will require a force option
> -----------------------------------------------------------------------
>                 Key: YARN-6509
>                 URL: https://issues.apache.org/jira/browse/YARN-6509
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Siddharth Seth
>            Assignee: Xuan Gong
>             Fix For: 2.9.0
>         Attachments: YARN-6509.1.patch
> An accidental fetch for a long running application can lead to scenario which the large
size of log can fill up a disk.

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