beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vikas Kedigehalli (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (BEAM-1631) Flink runner: submit job to a Flink-on-YARN cluster
Date Sat, 22 Apr 2017 00:17:04 GMT

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

Vikas Kedigehalli commented on BEAM-1631:
-----------------------------------------

[~aljoscha] I was able to come up with something without the need to have a bin/flink installation,
https://github.com/vikkyrk/incubator-beam/commit/7405d376db390aab0f4b658b34c35b2e50eca63b
(just a hack, needs clean up) but it still require users to have a {{HADOOP_CONF_DIR}}. If
we want to go with my approach then I am happy to clean up and send out a PR. 

> Flink runner: submit job to a Flink-on-YARN cluster
> ---------------------------------------------------
>
>                 Key: BEAM-1631
>                 URL: https://issues.apache.org/jira/browse/BEAM-1631
>             Project: Beam
>          Issue Type: New Feature
>          Components: runner-flink
>            Reporter: Davor Bonaci
>            Assignee: Aljoscha Krettek
>
> As far as I understand, running Beam pipelines on a Flink cluster can be done in two
ways:
> * Run directly with a Flink runner, and specifying {{--flinkMaster}} pipeline option
via, say, {{mvn exec}}.
> * Produce a bundled JAR, and use {{bin/flink}} to submit the same pipeline.
> These two ways are equivalent, and work well on a standalone Flink cluster.
> Submitting to a Flink-on-YARN is more complicated. You can still produce a bundled JAR,
and use {{bin/flink -yid <applicationid>}} to submit such a job. However, that seems
impossible with a Flink runner directly.
> If so, we should add the ability to the Flink runner to submit a job to a Flink-on-YARN
cluster directly.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message