[GEODE-4995] ClusterStartupRule is inefficient when shutting down the cluster

• Type: Test
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.6.0
• Component/s: tests
• Labels: pull-request-available
• Assignee: Bruce J Schuchardt
• Reporter: Bruce J Schuchardt
• Created: 04/Apr/18 19:09
• Updated: 02/May/18 18:21
• Resolved: 09/Apr/18 22:05

Description

ClusterStartupRule is often used to create a locator and some number of servers, ignoring the locator started by DUnitLauncher. This is inefficient but it's probably intentional and can be avoided by configuring the servers to use the DUnitLauncher's locator.

However, when shutting down the cluster it is managing ClusterStartupRule shuts down the VMs in order starting with vm0. If vm0 happens to be the membership coordinator this causes membership to create a new coordinator in vm1 and causes distributed lock grantor state to also fail over to vm1. Then vm1 is shut down, causing services to fail over to vm2. Etc.

ClusterStartupRule should be modified to shut down non-locator VMs first and then shut down locator VMs.

Issue Links

• links to: GitHub Pull Request #1736