[GEODE-4643] Shutdown command should reliably terminate members

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: gfsh, management
• Assignee: Unassigned
• Reporter: Patrick Rhomberg
• Created: 08/Feb/18 22:46
• Updated: 16/Feb/18 17:41

Description

Shutdown of a member is asynchronous. The shutdown command will trigger shutdown, but not guarantee it.

Beyond the obvious benefit of guaranteeing cluster state, this has also proven problematic in the runAll task of the geode-examples repository, as subsequent tests can begin before the previous test has finished tearing down.

---

Update:

The addition of wait tasks in GEODE-4666 have not resolved the CI failures in the geode-examples gradle task runAll. This suggests that the shutdown command can fail to actually stop all members. Due to an error in the initial commit of GEODE-4666, the 10 second timeout was ignored, resulting in a ~45 minute timeout in Travis. As such, is it reasonable to believe that shutdown either failed entirely or never executed on at least one member.

Issue Links

• is related to: GEODE-4666 CI failures in geode examples - Network is unreachable; port (10334) is not available on localhost
• relates to: GEODE-2391 change stop commands to be synchronous