[ 
https://issues.apache.org/jira/browse/FLINK-8818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16387511#comment-16387511
 ] 

ASF GitHub Bot commented on FLINK-8818:
---------------------------------------

Github user NicoK commented on the issue:

    https://github.com/apache/flink/pull/5601
  
    Different FS implementations try to circumvent the problem (or not), e.g. 
Presto's implementation implements the retries itself whenever it cannot find 
an object, while Hadoop's implementation did not (may depend on the version and 
may be subject to change).
    Also I don't know what the guarantees say about someone else reading your 
write - that would be the actual real usecase: artefact uploading by the 
client, downloading the artefacts via yarn on the worker nodes.


> Harden YarnFileStageTest upload test for eventual consistent read-after-write
> -----------------------------------------------------------------------------
>
>                 Key: FLINK-8818
>                 URL: https://issues.apache.org/jira/browse/FLINK-8818
>             Project: Flink
>          Issue Type: Sub-task
>          Components: FileSystem, Tests, YARN
>    Affects Versions: 1.5.0
>            Reporter: Nico Kruber
>            Assignee: Nico Kruber
>            Priority: Blocker
>             Fix For: 1.5.0, 1.4.3
>
>




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

Reply via email to