geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Patrick Rhomberg (JIRA)" <>
Subject [jira] [Updated] (GEODE-4643) Shutdown command should reliably terminate members
Date Fri, 16 Feb 2018 17:42:00 GMT


Patrick Rhomberg updated GEODE-4643:
    Summary: Shutdown command should reliably terminate members  (was: Shutdown command should
(optionally) wait for shutdown)

> Shutdown command should reliably terminate members
> --------------------------------------------------
>                 Key: GEODE-4643
>                 URL:
>             Project: Geode
>          Issue Type: Bug
>          Components: gfsh, management
>            Reporter: Patrick Rhomberg
>            Priority: Major
> 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.

This message was sent by Atlassian JIRA

View raw message