hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (Jira)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-17181) Handle transient stream read failures in FileSystem contract tests
Date Wed, 09 Sep 2020 11:01:00 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-17181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17192788#comment-17192788

Steve Loughran commented on HADOOP-17181:

fixed forever in Seek test; in Unbuffer we warn it may be transient. If it keeps happening
I may sit down and do the work to make it go away forever, while not devaluing the test entirely

> Handle transient stream read failures in FileSystem contract tests
> ------------------------------------------------------------------
>                 Key: HADOOP-17181
>                 URL: https://issues.apache.org/jira/browse/HADOOP-17181
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/s3
>    Affects Versions: 3.3.0
>            Reporter: Steve Loughran
>            Priority: Minor
>              Labels: pull-request-available
>          Time Spent: 1h 10m
>  Remaining Estimate: 0h
> Seen 2x recently, failure in ITestS3AContractUnbuffer as not enough data came back in
the read. 
> The contract test assumes that stream.read() will return everything, but it could be
some buffering problem. Proposed: switch to ReadFully to see if it is a quirk of the read/get
or is something actually wrong with the production code.

This message was sent by Atlassian Jira

To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org

View raw message