You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-dev@hadoop.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2013/08/28 02:29:54 UTC

[jira] [Created] (YARN-1111) NM containerlogs servlet can't handle logs of more than a GB

Steve Loughran created YARN-1111:
------------------------------------

             Summary: 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: Bug
          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