You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "YuFeng Shen (JIRA)" <ji...@apache.org> on 2018/09/01 15:32:00 UTC
[jira] [Updated] (FLINK-10274) The stop-cluster.sh cannot stop
cluster properly when there are multiple clusters running
[ https://issues.apache.org/jira/browse/FLINK-10274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
YuFeng Shen updated FLINK-10274:
--------------------------------
Description:
When you are prepare to do a Flink framework version upgrading by using the strategy [shadow copy|https://ci.apache.org/projects/flink/flink-docs-release-1.6/ops/upgrading.html#upgrading-the-flink-framework-version] , you have to run multiple clusters concurrently, however when you are ready to stop the old version cluster after upgrading, you would find the stop-cluster.sh wouldn't work as you expected, the following is the steps to duplicate the issue:
# There is already a running Flink 1.5.x cluster instance;
# Installing another Flink 1.6.x cluster instance at the same cluster machines;
# Migrating the jobs from Flink 1.5.x to Flink 1.6.x ;
# go to the bin dir of the Flink 1.5.x cluster instance and run stop-cluster.sh ;
You would expect the old Flink 1.5.x cluster instance be stopped ,right? Unfortunately the stopped cluster is the new installed Flink 1.6.x cluster instance instead!
was:
**When you are prepare to do a Flink framework version upgrading by using the strategy [shadow copy|https://ci.apache.org/projects/flink/flink-docs-release-1.6/ops/upgrading.html#upgrading-the-flink-framework-version] , then you need to run multiple clusters concurrently, however when you want to stop the old version cluster after upgrading ,you would find the stop-cluster.sh wouldn't work as you expected, the following is the steps to duplicate the issue:
# There is already a running Flink 1.5.x cluster instance
# Installing another Flink 1.6.x cluster instance at the same cluster machines
# Migrating the jobs from Flink 1.5.x to Flink 1.6.x
# go to the bin dir of the Flink 1.5.x cluster instance and run stop-cluster.sh
You expect the old Flink 1.5.x cluster instance would be stopped ,right? Unfortunately the stopped cluster is the new installed Flink 1.6.x cluster instance!
> The stop-cluster.sh cannot stop cluster properly when there are multiple clusters running
> -----------------------------------------------------------------------------------------
>
> Key: FLINK-10274
> URL: https://issues.apache.org/jira/browse/FLINK-10274
> Project: Flink
> Issue Type: Bug
> Components: Configuration
> Affects Versions: 1.5.1, 1.5.2, 1.5.3, 1.6.0
> Reporter: YuFeng Shen
> Assignee: YuFeng Shen
> Priority: Major
>
> When you are prepare to do a Flink framework version upgrading by using the strategy [shadow copy|https://ci.apache.org/projects/flink/flink-docs-release-1.6/ops/upgrading.html#upgrading-the-flink-framework-version] , you have to run multiple clusters concurrently, however when you are ready to stop the old version cluster after upgrading, you would find the stop-cluster.sh wouldn't work as you expected, the following is the steps to duplicate the issue:
> # There is already a running Flink 1.5.x cluster instance;
> # Installing another Flink 1.6.x cluster instance at the same cluster machines;
> # Migrating the jobs from Flink 1.5.x to Flink 1.6.x ;
> # go to the bin dir of the Flink 1.5.x cluster instance and run stop-cluster.sh ;
> You would expect the old Flink 1.5.x cluster instance be stopped ,right? Unfortunately the stopped cluster is the new installed Flink 1.6.x cluster instance instead!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)