hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sunil Govindan (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-2024) IOException in AppLogAggregatorImpl does not give stacktrace and leaves aggregated TFile in a bad state.
Date Sat, 17 Nov 2018 03:24:08 GMT

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

Sunil Govindan updated YARN-2024:
    Target Version/s: 3.3.0  (was: 3.2.0)

Bulk update: moved all 3.2.0 non-blocker issues, please move back if it is a blocker.

> IOException in AppLogAggregatorImpl does not give stacktrace and leaves aggregated TFile
in a bad state.
> --------------------------------------------------------------------------------------------------------
>                 Key: YARN-2024
>                 URL: https://issues.apache.org/jira/browse/YARN-2024
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: log-aggregation
>    Affects Versions: 0.23.10, 2.4.0
>            Reporter: Eric Payne
>            Assignee: Xuan Gong
>            Priority: Major
> Multiple issues were encountered when AppLogAggregatorImpl encountered an IOException
in AppLogAggregatorImpl#uploadLogsForContainer while aggregating yarn-logs for an application
that had very large (>150G each) error logs.
> - An IOException was encountered during the LogWriter#append call, and a message was
printed, but no stacktrace was provided. Message: "ERROR: Couldn't upload logs for container_nnnnnnnnnnnnn_nnnnnnn_nn_nnnnnn.
Skipping this container."
> - After the IOExceptin, the TFile is in a bad state, so subsequent calls to LogWriter#append
fail with the following stacktrace:
> 2014-04-16 13:29:09,772 [LogAggregationService #17907] ERROR org.apache.hadoop.yarn.YarnUncaughtExceptionHandler:
Thread Thread[LogAggregationService #17907,5,main] threw an Exception.
> java.lang.IllegalStateException: Incorrect state to start a new key: IN_VALUE
>         at org.apache.hadoop.io.file.tfile.TFile$Writer.prepareAppendKey(TFile.java:528)
>         at org.apache.hadoop.yarn.logaggregation.AggregatedLogFormat$LogWriter.append(AggregatedLogFormat.java:262)
>         at org.apache.hadoop.yarn.server.nodemanager.containermanager.logaggregation.AppLogAggregatorImpl.uploadLogsForContainer(AppLogAggregatorImpl.java:128)
>         at org.apache.hadoop.yarn.server.nodemanager.containermanager.logaggregation.AppLogAggregatorImpl.doAppLogAggregation(AppLogAggregatorImpl.java:164)
> ...
> - At this point, the yarn-logs cleaner still thinks the thread is aggregating, so the
huge yarn-logs never get cleaned up for that application.

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