You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Ufuk Celebi (JIRA)" <ji...@apache.org> on 2016/04/20 16:35:25 UTC
[jira] [Commented] (FLINK-3791) Flink CLI must has arguments to
specify zookeeper cluster required to work with Standalone HA cluster
[ https://issues.apache.org/jira/browse/FLINK-3791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15250002#comment-15250002 ]
Ufuk Celebi commented on FLINK-3791:
------------------------------------
I agree. There is an issue for it here: FLINK-3091. I think we should definitely address this for 1.1, maybe even 1.0.x.
I'm closing this a duplicate of FLINK-3091.
> Flink CLI must has arguments to specify zookeeper cluster required to work with Standalone HA cluster
> -----------------------------------------------------------------------------------------------------
>
> Key: FLINK-3791
> URL: https://issues.apache.org/jira/browse/FLINK-3791
> Project: Flink
> Issue Type: Improvement
> Components: Command-line client
> Affects Versions: 1.0.1
> Reporter: Maxim Dobryakov
>
> Flink CLI can't connect to Standalone HA Flink cluster use command line arguments only (problem described [here|http://stackoverflow.com/questions/36625742/cant-deploy-flow-to-ha-cluster-of-apache-flink-using-flink-cli]).
> It is cause a big problem: if I want to deploy flow to different environments (staging, production, etc) I *must* generate different `flink-conf.yaml` files before run Flink CLI. This is horrible I think. Will be better to have command line arguments to specify zookeepr cluster in Flink CLI.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)