hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gabor Bota (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-15239) S3ABlockOutputStream.flush() be no-op when stream closed
Date Fri, 13 Apr 2018 15:04:00 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-15239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Gabor Bota updated HADOOP-15239:
--------------------------------
    Status: Open  (was: Patch Available)

> S3ABlockOutputStream.flush() be no-op when stream closed
> --------------------------------------------------------
>
>                 Key: HADOOP-15239
>                 URL: https://issues.apache.org/jira/browse/HADOOP-15239
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/s3
>    Affects Versions: 3.0.0, 2.7.5, 2.8.3, 2.9.0
>            Reporter: Steve Loughran
>            Assignee: Gabor Bota
>            Priority: Trivial
>         Attachments: HADOOP-15239.001.patch, HADOOP-15239.002.patch
>
>
> when you call flush() on a closed S3A output stream, you get a stack trace. 
> This can cause problems in code with race conditions across threads, e.g. FLINK-8543.

> we could make it log@warn "stream closed" rather than raise an IOE. It's just a hint,
after all.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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


Mime
View raw message