hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kumar Vavilapalli (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-1111) NM containerlogs servlet can't handle logs of more than a GB
Date Sun, 01 Sep 2013 23:33:52 GMT

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

Vinod Kumar Vavilapalli updated YARN-1111:

    Issue Type: Sub-task  (was: Bug)
        Parent: YARN-431
> NM containerlogs servlet can't handle logs of more than a GB
> ------------------------------------------------------------
>                 Key: YARN-1111
>                 URL: https://issues.apache.org/jira/browse/YARN-1111
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: nodemanager
>    Affects Versions: 2.1.0-beta
>         Environment: Long-lived service generating lots of log data from HBase running
in debug level
>            Reporter: Steve Loughran
>            Priority: Minor
> If a container is set up to log stdout to a file, the container log servlet will list
the file
> {code}
> err.txt : Total file length is 551 bytes.
> out.txt : Total file length is 1572099246 bytes.
> {code}
> If you actually click on out.txt then the tail logic takes a *very* long time to react.
There is also the question of what will happen if the log fills up that volume

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message