[
https://issues.apache.org/jira/browse/HADOOP-16906?focusedWorklogId=548831&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-548831
]
ASF GitHub Bot logged work on HADOOP-16906:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 05/Feb/21 19:52
Start Date: 05/Feb/21 19:52
Worklog Time Spent: 10m
Work Description: steveloughran commented on pull request #2684:
URL: https://github.com/apache/hadoop/pull/2684#issuecomment-774252596
test run against s3 london; known failures... buffer underfill and a recent
s3 change breaking ITestAssumeRole. Both unrelated
```
[ERROR]
ITestS3AContractUnbuffer>AbstractContractUnbufferTest.testUnbufferBeforeRead:63->AbstractContractUnbufferTest.validateFullFileContents:132->AbstractContractUnbufferTest.validateFileContents:139->Assert.assertEquals:645->Assert.failNotEquals:834->Assert.fail:88
failed to read expected number of bytes from stream. This may be transient
expected:<1024> but was:<3>
[ERROR]
ITestAssumeRole.testAssumeRoleBadInnerAuth:256->expectFileSystemCreateFailure:136
Expected to find 'not a valid key=value pair (missing equal-sign) in
Authorization header' but got unexpected exception:
org.apache.hadoop.fs.s3a.AWSBadRequestException: Instantiate
org.apache.hadoop.fs.s3a.auth.AssumedRoleCredentialProvider:
com.amazonaws.services.securitytoken.model.AWSSecurityTokenServiceException:
null (Service: AWSSecurityTokenService; Status Code: 400; Error Code:
IncompleteSignature; Request ID: 9050b674-e236-4b4c-8831-21149db759bc; Proxy:
null):IncompleteSignature: null (Service: AWSSecurityTokenService; Status Code:
400; Error Code: IncompleteSignature; Request ID:
9050b674-e236-4b4c-8831-21149db759bc; Proxy: null)
```
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 548831)
Time Spent: 3h (was: 2h 50m)
> Add some Abortable.abort() interface for streams etc which can be terminated
> ----------------------------------------------------------------------------
>
> Key: HADOOP-16906
> URL: https://issues.apache.org/jira/browse/HADOOP-16906
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs, fs/azure, fs/s3
> Affects Versions: 3.3.0
> Reporter: Steve Loughran
> Assignee: Jungtaek Lim
> Priority: Blocker
> Labels: pull-request-available
> Time Spent: 3h
> Remaining Estimate: 0h
>
> Some IO we want to be able to abort rather than close cleanly, especially if
> the inner stream is an HTTP connection which itself supports some abort()
> method. For example: uploads to an object where we want to cancel the upload
> without close() making an incomplete write visible.
> Proposed: Add a generic interface which things like streams can implement
> {code}
> AbortableIO {
> public void abortIO() throws IOE;
> }
> {code}
> +do for s3a output stream. I wouldn't do this a passthrough on
> FSDataOutputStream because we need to consider what expectations callers have
> of an operation being "aborted"
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
