[ 
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 auto-deprioritized-minor 
pull-request-available  (was: auto-deprioritized-major pull-request-available 
stale-minor)
    Priority: Not a Priority  (was: Minor)

This issue was labeled "stale-minor" 7 days ago and has not received any 
updates so it is being deprioritized. If this ticket is actually Minor, please 
raise the priority and ask a committer to assign you the issue or revive the 
public discussion.


> 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: Not a Priority
>              Labels: auto-deprioritized-major, auto-deprioritized-minor, 
> pull-request-available
>
> [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)

Reply via email to