[
https://issues.apache.org/jira/browse/FLINK-6000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephan Ewen resolved FLINK-6000.
---------------------------------
Resolution: Fixed
Fix Version/s: 1.2.1
1.3.0
Fixed in
- 1.2.1 via d398205edbdf1e76569e6508be1066243e7b1101
- 1.3.0 via 034d9a3ab8bb7dec57a7021564060274760ed339
> Can not start HA cluster with start-cluster.sh
> ----------------------------------------------
>
> Key: FLINK-6000
> URL: https://issues.apache.org/jira/browse/FLINK-6000
> Project: Flink
> Issue Type: Bug
> Components: Startup Shell Scripts
> Affects Versions: 1.2.0
> Reporter: Dawid Wysakowicz
> Assignee: Dawid Wysakowicz
> Fix For: 1.3.0, 1.2.1
>
>
> Right know it is impossible to start a cluster in zookeeper HA mode as
> described in the documentation by setting:
> in con/flink-conf.yaml:
> {code}
> high-availability: zookeeper
> ...
> {code}
> in conf/masters:
> {code}
> localhost:8081
> localhost:8082
> {code}
> The problem is with the {{bin/config.sh}} file. If value "zookeeper" is read
> from config file the variable {{HIGH_AVAILABILITY}} will be reset to "none"
> with the else branch. See the below code:
> {code}
> if [ -z "${HIGH_AVAILABILITY}" ]; then
> HIGH_AVAILABILITY=$(readFromConfig ${KEY_HIGH_AVAILABILITY} ""
> "${YAML_CONF}")
> if [ -z "${HIGH_AVAILABILITY}" ]; then
> # Try deprecated value
> DEPRECATED_HA=$(readFromConfig "recovery.mode" "" "${YAML_CONF}")
> if [ -z "${DEPRECATED_HA}" ]; then
> HIGH_AVAILABILITY="none"
> elif [ ${DEPRECATED_HA} == "standalone" ]; then
> # Standalone is now 'none'
> HIGH_AVAILABILITY="none"
> else
> HIGH_AVAILABILITY=${DEPRECATED_HA}
> fi
> else
> HIGH_AVAILABILITY="none" <-- it exits here
> fi
> fi
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
