You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Stefano Baghino (JIRA)" <ji...@apache.org> on 2016/03/29 15:24:25 UTC

[jira] [Created] (FLINK-3675) YARN ship folder incosistent behavior

Stefano Baghino created FLINK-3675:
--------------------------------------

             Summary: YARN ship folder incosistent behavior
                 Key: FLINK-3675
                 URL: https://issues.apache.org/jira/browse/FLINK-3675
             Project: Flink
          Issue Type: Bug
          Components: YARN Client
    Affects Versions: 1.0.0
            Reporter: Stefano Baghino


After [some discussion on the user mailing list|http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Flink-and-YARN-ship-folder-td5458.html] it came up that the {{flink/lib}} folder is always supposed to be shipped to the YARN cluster so that all the nodes have access to its contents.

Currently however, the Flink long-running YARN session actually ships the folder because it's explicitly specified in the {{yarn-session.sh}} script, while running a single job on YARN does not automatically ship it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)