geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jinmei Liao (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GEODE-3053) gfsh hangs when starting locator
Date Thu, 27 Jul 2017 17:27:00 GMT

    [ https://issues.apache.org/jira/browse/GEODE-3053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16103542#comment-16103542
] 

Jinmei Liao commented on GEODE-3053:
------------------------------------

looks like we need to two hosts (machines), in host1, we are starting up a locator trying
to join the locator on host2, and in host2, we are starting a locator trying to join host1,
and then we keep stop/start these locators on these two hosts. Then it hangs somehow. 

> gfsh hangs when starting locator
> --------------------------------
>
>                 Key: GEODE-3053
>                 URL: https://issues.apache.org/jira/browse/GEODE-3053
>             Project: Geode
>          Issue Type: Bug
>          Components: gfsh
>    Affects Versions: 1.1.1
>            Reporter: Anton Mironenko
>            Assignee: Kirk Lund
>            Priority: Minor
>         Attachments: 20170608-host1-gfsh-hangs.zip, 20170608-host2-gfsh-hangs.zip, gfsh-26286-jstack.log
>
>
> Sometimes when a locator is started via gfsh, gfsh hangs forever.
> This happens on Geode 1.1.1 (not sure about 1.2 and 1.3, probably the same issue is there).
> Here are the instructions how to reproduce.
> Test preparation:
> ---------------------
> Here are two attached zip files - "20170608-host1-gfsh-hangs.zip" and "20170608-host2-gfsh-hangs"
> 1) unzip "20170608-host1-gfsh-hangs.zip" into some folder on your first host
> 2) in start-locator.sh change the IPs of locators to the values of your host1 and host2
> "--locators=10.50.3.38[20236],10.50.3.14[20236]"
> 3) do the bullets 1)-2) for host2, the folder where you unzip the file should be the
same as on the first host
> Test running:
> ---------------
> 1) rm -rf
> {locator0,server1}
> 2) run ./restart-cycle.sh on host1, then on host2. 
> 3) observe this test running until you see a lot of dots in the shell, which means the
gfsh hanged. Usually it takes not more than 10 minutes.
> Here is also the stack trace of hanged gfsh (java process org.apache.geode.management.internal.cli.Launcher),
see attached "gfsh-26286-jstack"



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message