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 "Zhankun Tang (Jira)" <ji...@apache.org> on 2019/08/26 14:17:00 UTC
[jira] [Updated] (YARN-9607) Auto-configuring rollover-size of
IFile format for non-appendable filesystems
[ https://issues.apache.org/jira/browse/YARN-9607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Zhankun Tang updated YARN-9607:
-------------------------------
Target Version/s: 3.3.0, 3.2.1, 3.1.4 (was: 3.3.0, 3.2.1, 3.1.3)
> Auto-configuring rollover-size of IFile format for non-appendable filesystems
> -----------------------------------------------------------------------------
>
> Key: YARN-9607
> URL: https://issues.apache.org/jira/browse/YARN-9607
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: log-aggregation, yarn
> Affects Versions: 3.3.0
> Reporter: Adam Antal
> Assignee: Adam Antal
> Priority: Major
> Attachments: YARN-9607.001.patch, YARN-9607.002.patch
>
>
> In YARN-9525, we made IFile format compatible with remote folders with s3a scheme. In rolling fashioned log-aggregation IFile still fails with the "append is not supported" error message, which is a known limitation of the format by design.
> There is a workaround though: setting the rollover size in the configuration of the IFile format, in each rolling cycle a new aggregated log file will be created, thus we eliminated the append from the process. Setting this config globally would cause performance problems in the regular log-aggregation, so I'm suggesting to enforcing this config to zero, if the scheme of the URI is s3a (or any other non-appendable filesystem).
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org