[jira] [Updated] (HADOOP-17928) s3a: set fs.s3a.downgrade.syncable.exceptions = true by default
[ https://issues.apache.org/jira/browse/HADOOP-17928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chao Sun updated HADOOP-17928: -- Target Version/s: 3.3.3 (was: 3.3.2) > 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 > 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: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-17928) s3a: set fs.s3a.downgrade.syncable.exceptions = true by default
[ https://issues.apache.org/jira/browse/HADOOP-17928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated HADOOP-17928: Labels: pull-request-available (was: ) > 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 > Time Spent: 10m > 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.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
