[
https://issues.apache.org/jira/browse/HADOOP-17928?focusedWorklogId=669978&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-669978
]
ASF GitHub Bot logged work on HADOOP-17928:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 26/Oct/21 09:36
Start Date: 26/Oct/21 09:36
Worklog Time Spent: 10m
Work Description: steveloughran commented on pull request #3585:
URL: https://github.com/apache/hadoop/pull/3585#issuecomment-951761021
Test result, all good except for the buffer incomplete issue which happens
locally for me
```
[ERROR] Failures:
[ERROR]
ITestS3AContractUnbuffer>AbstractContractUnbufferTest.testUnbufferBeforeRead:63->AbstractContractUnbufferTest.validateFullFileContents:132->AbstractContractUnbufferTest.validateFileContents:139->Assert.assertEquals:647->Assert.failNotEquals:835->Assert.fail:89
failed to read expected number of bytes from stream. This may be transient
expected:<1024> but was:<515>
[INFO]
[ERROR] Tests run: 1471, Failures: 1, Errors: 0, Skipped: 302
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 669978)
Time Spent: 40m (was: 0.5h)
> 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: 40m
> 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: [email protected]
For additional commands, e-mail: [email protected]
