[
https://issues.apache.org/jira/browse/YARN-9607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16862988#comment-16862988
]
Szilard Nemeth commented on YARN-9607:
--------------------------------------
Oh, one more thing:
As you are overriding the config in
LogAggregationIndexedFileController.getRollOverLogMaxSize, at least you need to
log a statement that you overridden the value so users wouldn't be confused by
any chance why the value ended up to be zero.
Do you agree [~adam.antal]?
> 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
>
>
> 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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
