flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-6000) Can not start HA cluster with start-cluster.sh
Date Fri, 10 Mar 2017 08:19:04 GMT

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

ASF GitHub Bot commented on FLINK-6000:
---------------------------------------

GitHub user dawidwys opened a pull request:

    https://github.com/apache/flink/pull/3506

    [FLINK-6000] Fix starting HA cluster with start-cluster.sh

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/dawidwys/flink flink6000

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/flink/pull/3506.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #3506
    
----
commit 1b94be9d77a784012aab852bc4e51bff1c793009
Author: Dawid Wysakowicz <dawid@getindata.com>
Date:   2017-03-10T08:15:06Z

    [FLINK-6000] Fix starting HA cluster with start-cluster.sh

----


> 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
>
> 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)

Mime
View raw message