You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Anthony Baker (JIRA)" <ji...@apache.org> on 2016/01/08 02:37:39 UTC
[jira] [Updated] (GEODE-380) Using gfsh to shutdown a server can
result in an unclean shutdown under certain circumstances
[ https://issues.apache.org/jira/browse/GEODE-380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Anthony Baker updated GEODE-380:
--------------------------------
Fix Version/s: (was: 1.0.0-incubating)
1.0.0-alpha1
> Using gfsh to shutdown a server can result in an unclean shutdown under certain circumstances
> ---------------------------------------------------------------------------------------------
>
> Key: GEODE-380
> URL: https://issues.apache.org/jira/browse/GEODE-380
> Project: Geode
> Issue Type: Bug
> Components: management
> Affects Versions: 1.0.0-incubating
> Reporter: Jens Deppe
> Assignee: Jens Deppe
> Priority: Minor
> Labels: gfsh
> Fix For: 1.0.0-alpha1
>
>
> Occasionally, when the dev REST API is enabled, and gfsh is used to shutdown a server, the server does not shutdown cleanly and exits early.
> This can be seen even more frequently (almost 100%) when the system property {{gemfire.disableShutdownHook}} is set.
> This may not appear as a problem in most cases, however if {{network-partition-detection}} is enabled then other members will see this as a member crashing and may disconnect themselves from the cluster in order to avoid a split brain.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)