[FLINK-10274] The stop-cluster.sh cannot stop cluster properly when there are multiple clusters running

• Type: Bug
• Status: Open
• Priority: Not a Priority
• Resolution: Unresolved
• Affects Version/s: 1.5.1, 1.5.2, 1.5.3, 1.6.0
• Component/s: Runtime / Configuration
• Labels: auto-deprioritized-major auto-deprioritized-minor auto-unassigned pull-request-available
• Assignee: Unassigned
• Reporter: YuFeng Shen
• Created: 31/Aug/18 16:23
• Updated: 27/Dec/21 10:47

Description

When you are preparing to do a Flink framework version upgrading by using the strategy shadow copy , 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:

1. There is already a running Flink 1.5.x cluster instance;
2. Installing another Flink 1.6.x cluster instance at the same cluster machines;
3. Migrating the jobs from Flink 1.5.x  to Flink 1.6.x ;
4. 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!

Issue Links

• links to: GitHub Pull Request #14014