You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Flink Jira Bot (Jira)" <ji...@apache.org> on 2022/04/07 22:39:00 UTC

[jira] [Updated] (FLINK-20918) Avoid excessive flush of Hadoop output stream

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

Flink Jira Bot updated FLINK-20918:
-----------------------------------
    Labels: auto-deprioritized-major pull-request-available stale-minor  (was: auto-deprioritized-major pull-request-available)

I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help the community manage its development. I see this issues has been marked as Minor but is unassigned and neither itself nor its Sub-Tasks have been updated for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is still Minor, please either assign yourself or give an update. Afterwards, please remove the label or in 7 days the issue will be deprioritized.


> Avoid excessive flush of Hadoop output stream
> ---------------------------------------------
>
>                 Key: FLINK-20918
>                 URL: https://issues.apache.org/jira/browse/FLINK-20918
>             Project: Flink
>          Issue Type: Bug
>          Components: Connectors / Hadoop Compatibility, FileSystems
>    Affects Versions: 1.11.3, 1.12.0
>            Reporter: Paul Lin
>            Priority: Minor
>              Labels: auto-deprioritized-major, pull-request-available, stale-minor
>
> [HadoopRecoverableFsDataOutputStream#sync|https://github.com/apache/flink/blob/67d167ccd45046fc5ed222ac1f1e3ba5e6ec434b/flink-filesystems/flink-hadoop-fs/src/main/java/org/apache/flink/runtime/fs/hdfs/HadoopRecoverableFsDataOutputStream.java#L123] calls both `hflush` and `hsync`, whereas `hsync` is an enhanced version of `hflush`. We should remove the `hflush` call to avoid the excessive flush.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)