[
https://issues.apache.org/jira/browse/HADOOP-17928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran resolved HADOOP-17928.
-------------------------------------
Fix Version/s: 3.3.2
Resolution: Fixed
> s3a: set fs.s3a.downgrade.syncable.exceptions = true by default
> ---------------------------------------------------------------
>
> Key: HADOOP-17928
> URL: https://issues.apache.org/jira/browse/HADOOP-17928
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 3.3.1
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Major
> Labels: pull-request-available
> Fix For: 3.3.2
>
> Time Spent: 3.5h
> Remaining Estimate: 0h
>
> HADOOP-17597 set policy of reacting to hsync() on an s3 output stream to be
> one of :Fail, warn, with default == fail.
> I propose downgrading this to warn. We've done it internally, after having it
> on fail long enough to identify which processes were doing either of
> * having unrealistic expectations about the output stream (fix: move off s3)
> * were using hflush() as a variant of flush(), with the failure being an
> over-reaction
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
