[
https://issues.apache.org/jira/browse/YARN-9607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16867857#comment-16867857
]
Steve Loughran commented on YARN-9607:
--------------------------------------
HADOOP-15691 proposes adding a new method, getPathCapabilities to allow you
check exactly that. Sadly, its received approximate 0 reviews, and is only
something I'm working on in my spare time.
I would like to see it in, and given that YARN is shipped in sync with
everything else, now is a good time for other people to offer to get in
involved in this
If I offer to update that patch, who in this JIRA discussion promises to review
it with a goal of getting it committed? As once it is in, the check would as
simple as
{code}
if (fs.hasPathCapability("fs.feature.append", path)) {
...
} else {
//fallback
}
{code}
that's it: no need to second guess things downstream, write code which only
works on some stores, as determined by trial and error and support calls.
But: if nobody puts their hand up to say "I need this and will help get it in"
-you aren't going to get it
> 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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
