You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Prabhu Joseph (Jira)" <ji...@apache.org> on 2020/06/17 09:21:00 UTC
[jira] [Updated] (YARN-8106) Update
LogAggregationIndexedFileController to use readFully instead read to avoid
IOException while loading log meta
[ https://issues.apache.org/jira/browse/YARN-8106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Prabhu Joseph updated YARN-8106:
--------------------------------
Summary: Update LogAggregationIndexedFileController to use readFully instead read to avoid IOException while loading log meta (was: Update LogAggregationIndexedFileController to use readFull instead read to avoid IOException while loading log meta)
> Update LogAggregationIndexedFileController to use readFully instead read to avoid IOException while loading log meta
> --------------------------------------------------------------------------------------------------------------------
>
> Key: YARN-8106
> URL: https://issues.apache.org/jira/browse/YARN-8106
> Project: Hadoop YARN
> Issue Type: Bug
> Components: log-aggregation
> Reporter: Prabhu Joseph
> Assignee: Prabhu Joseph
> Priority: Critical
> Fix For: 3.1.1
>
> Attachments: YARN-8106.1.patch
>
>
> yarn logs command fails with below error message. Found LogAggregationIndexedFileController uses read() to read the contents of remoteLog into byte array which sometimes does not read full contents and so actual bytes read is not same as offset leading to IOException. readFully() can be used.
> {code}
> WARN ifile.LogAggregationIndexedFileController: Can not get log meta from the log
> Error on loading log meta from
> if (actual != offset) {
> throw new IOException("Error on loading log meta from "
> + remoteLogPath);
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org