flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maximilian Michels (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-3675) YARN ship folder incosistent behavior
Date Mon, 27 Jun 2016 13:46:52 GMT

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

Maximilian Michels commented on FLINK-3675:

Woops. Not enough coffee today ;) Yes, I meant option 1!

The Flink assembly has to be in the /lib folder (or specified via {{-yj}}) but it is still
shipped even if the lib folder is not shipped. Otherwise, we wouldn't be able to run any Flink
clusters using {{./flink -m yarn-cluster}} because the /lib folder is currently not shipped

> 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

View raw message