[
https://issues.apache.org/jira/browse/FLINK-3675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maximilian Michels resolved FLINK-3675.
---------------------------------------
Resolution: Fixed
Fixed via 0483ba583c7790d13b8035c2916318a2b58c67d6
> 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
> Assignee: Maximilian Michels
> Priority: Critical
> Fix For: 1.1.0
>
>
> 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)
