[ https://issues.apache.org/jira/browse/FLINK-3675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15350951#comment-15350951 ]
Maximilian Michels edited comment on FLINK-3675 at 6/27/16 1:04 PM: -------------------------------------------------------------------- Do we want 1) to ship the /lib folder even if the user specifies a ship folder manually (via `-yt`)? Or do we want 2) to overwrite the default lib folder with the user location (as it is now for {{yarn-session.sh}})? was (Author: mxm): Do we want to ship the /lib folder even if the user specifies a ship folder manually (via `-yt`)? Or do we want to overwrite the default lib folder with the user location (as it is now for {{yarn-session.sh}})? > 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)