geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jacob S. Barrett (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (GEODE-2160) gfsh stop server/locator exits with code 0 before server/locator actually stops
Date Thu, 01 Dec 2016 01:18:58 GMT

     [ https://issues.apache.org/jira/browse/GEODE-2160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jacob S. Barrett updated GEODE-2160:
------------------------------------
    Description: 
Executing
{code}
gfsh stop server --name=server1
{code}
{{gfsh}} exits, with code 0, prior to the server actually being stopped.

This behavior isn't documented and makes scripting with gfsh difficult. One can't assume that
the server has stopped after gfsh exits. To verify you must parse the server pid and check
the status of the proc. 

Simple test:
{code}
gfsh start server --name=s2 && sleep 10 && gfsh stop server --dir=s2; echo
$?; while (kill -0 `cat s2/vf.gf.server.pid`); do date +%s.%N; done
{code}
Starts server, waits 10s, stops server, prints exit code, loops until process is gone while
printing the time since epoch.



  was:
Executing
{code}
gfsh stop server --name=server1
{code}
{{gfsh}} exits, with code 0, prior to the server actually being stopped.

Simple test:
{code}
gfsh start server --name=s2 && sleep 10 && gfsh stop server --dir=s2; echo
$?; while (kill -0 `cat s2/vf.gf.server.pid`); do date +%s.%N; done
{code}
Starts server, waits 10s, stops server, prints exit code, loops until process is gone while
printing the time since epoch.




> gfsh stop server/locator exits with code 0 before server/locator actually stops
> -------------------------------------------------------------------------------
>
>                 Key: GEODE-2160
>                 URL: https://issues.apache.org/jira/browse/GEODE-2160
>             Project: Geode
>          Issue Type: Bug
>    Affects Versions: 1.0.0-incubating
>            Reporter: Jacob S. Barrett
>
> Executing
> {code}
> gfsh stop server --name=server1
> {code}
> {{gfsh}} exits, with code 0, prior to the server actually being stopped.
> This behavior isn't documented and makes scripting with gfsh difficult. One can't assume
that the server has stopped after gfsh exits. To verify you must parse the server pid and
check the status of the proc. 
> Simple test:
> {code}
> gfsh start server --name=s2 && sleep 10 && gfsh stop server --dir=s2;
echo $?; while (kill -0 `cat s2/vf.gf.server.pid`); do date +%s.%N; done
> {code}
> Starts server, waits 10s, stops server, prints exit code, loops until process is gone
while printing the time since epoch.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message