服务器已从gfsh成功启动,但未连接到定位器

问题描述 投票:0回答:1

[我使用gfsh启动了一个geode定位器,然后再次使用gfsh启动了四台服务器,但是当我使用list Members命令时,我只获得了定位器,而不是服务器。

gfsh>start locator --name=locate --port=10334
Starting a Geode Locator in C:\Users\Milin\locate...
.
Locator in C:\Users\Milin\locate on DESKTOP-EMRTT29.hitronhub.home[10334] as locate is currently online.
Process ID: 1616
Uptime: 3 minutes 31 seconds
Geode Version: 1.11.0
Java Version: 13.0.2
Log File: C:\Users\Milin\locate\locate.log
JVM Arguments: -Dgemfire.enable-cluster-configuration=true -Dgemfire.load-cluster-configuration-from-dir=false -Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true -Dsun.rmi.dgc.server.gcInterval=9223372036854775806
Class-Path: C:\apache-geode-1.11.0\lib\geode-core-1.11.0.jar;C:\apache-geode-1.11.0\lib\geode-dependencies.jar

Successfully connected to: JMX Manager [host=DESKTOP-EMRTT29.hitronhub.home, port=1099]

Cluster configuration service is up and running.

gfsh>connect --locator=DESKTOP-EMRTT29.hitronhub.home[10334]
Already connected to: DESKTOP-EMRTT29.hitronhub.home[1099]

gfsh>list members
Member Count : 1

 Name  | Id
------ | -------------------------------------------------------------
locate | 192.168.0.82(locate:1616:locator)<ec><v0>:41000 [Coordinator]

gfsh>start server --name=serverA --server-port=41101
Starting a Geode Server in C:\Users\Milin\serverA...
.
Server in C:\Users\Milin\serverA on 192.168.0.82[41101] as serverA is currently online.
Process ID: 20920
Uptime: 20 minutes 13 seconds
Geode Version: 1.11.0
Java Version: 13.0.2
Log File: C:\Users\Milin\serverA\serverA.log
JVM Arguments: -Dgemfire.start-dev-rest-api=false -Dgemfire.use-cluster-configuration=true -XX:OnOutOfMemoryError=taskkill /F /PID %p -Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true -Dsun.rmi.dgc.server.gcInterval=9223372036854775806
Class-Path: C:\apache-geode-1.11.0\lib\geode-core-1.11.0.jar;C:\apache-geode-1.11.0\lib\geode-dependencies.jar

gfsh>start server --name=serverB --server-port=41102
Starting a Geode Server in C:\Users\Milin\serverB...
.
Server in C:\Users\Milin\serverB on DESKTOP-EMRTT29.hitronhub.home[41102] as serverB is currently online.
Process ID: 8908
Uptime: 20 minutes 17 seconds
Geode Version: 1.11.0
Java Version: 13.0.2
Log File: C:\Users\Milin\serverB\serverB.log
JVM Arguments: -Dgemfire.start-dev-rest-api=false -Dgemfire.use-cluster-configuration=true -XX:OnOutOfMemoryError=taskkill /F /PID %p -Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true -Dsun.rmi.dgc.server.gcInterval=9223372036854775806
Class-Path: C:\apache-geode-1.11.0\lib\geode-core-1.11.0.jar;C:\apache-geode-1.11.0\lib\geode-dependencies.jar

gfsh>start server --name=serverC --server-port=41103
Starting a Geode Server in C:\Users\Milin\serverC...
.
Server in C:\Users\Milin\serverC on DESKTOP-EMRTT29.hitronhub.home[41103] as serverC is currently online.
Process ID: 5940
Uptime: 20 minutes 15 seconds
Geode Version: 1.11.0
Java Version: 13.0.2
Log File: C:\Users\Milin\serverC\serverC.log
JVM Arguments: -Dgemfire.start-dev-rest-api=false -Dgemfire.use-cluster-configuration=true -XX:OnOutOfMemoryError=taskkill /F /PID %p -Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true -Dsun.rmi.dgc.server.gcInterval=9223372036854775806
Class-Path: C:\apache-geode-1.11.0\lib\geode-core-1.11.0.jar;C:\apache-geode-1.11.0\lib\geode-dependencies.jar

gfsh>start server --name=serverD --server-port=41104
Starting a Geode Server in C:\Users\Milin\serverD...
.
Server in C:\Users\Milin\serverD on DESKTOP-EMRTT29.hitronhub.home[41104] as serverD is currently online.
Process ID: 16548
Uptime: 20 minutes 12 seconds
Geode Version: 1.11.0
Java Version: 13.0.2
Log File: C:\Users\Milin\serverD\serverD.log
JVM Arguments: -Dgemfire.start-dev-rest-api=false -Dgemfire.use-cluster-configuration=true -XX:OnOutOfMemoryError=taskkill /F /PID %p -Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true -Dsun.rmi.dgc.server.gcInterval=9223372036854775806
Class-Path: C:\apache-geode-1.11.0\lib\geode-core-1.11.0.jar;C:\apache-geode-1.11.0\lib\geode-dependencies.jar

gfsh>list members
Member Count : 1

 Name  | Id
------ | -------------------------------------------------------------
locate | 192.168.0.82(locate:1616:locator)<ec><v0>:41000 [Coordinator]

然后我还尝试通过指定定位器名称(尝试使用名称和ID)来启动服务器,但结果仍然相同

gfsh>stop locator --name=locate
Stopping Locator running in C:\Users\Milin\locate on DESKTOP-EMRTT29.hitronhub.home[10334] as locate...
Process ID: 1616
Log File: C:\Users\Milin\locate\locate.log
....

No longer connected to DESKTOP-EMRTT29.hitronhub.home[1099].

No longer connected to DESKTOP-EMRTT29.hitronhub.home[1099].
gfsh>list members
Command 'list members' was found but is not currently available (type 'help' then ENTER to learn about this command)
gfsh>start locator --name=locate --port=10334
Starting a Geode Locator in C:\Users\Milin\locate...
..............................
Locator in C:\Users\Milin\locate on DESKTOP-EMRTT29.hitronhub.home[10334] as locate is currently online.
Process ID: 20936
Uptime: 19 seconds
Geode Version: 1.11.0
Java Version: 13.0.2
Log File: C:\Users\Milin\locate\locate.log
JVM Arguments: -Dgemfire.enable-cluster-configuration=true -Dgemfire.load-cluster-configuration-from-dir=false -Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true -Dsun.rmi.dgc.server.gcInterval=9223372036854775806
Class-Path: C:\apache-geode-1.11.0\lib\geode-core-1.11.0.jar;C:\apache-geode-1.11.0\lib\geode-dependencies.jar

Successfully connected to: JMX Manager [host=DESKTOP-EMRTT29.hitronhub.home, port=1099]

Cluster configuration service is up and running.

gfsh>list members
Member Count : 1

 Name  | Id
------ | --------------------------------------------------------------
locate | 192.168.0.82(locate:20936:locator)<ec><v0>:41000 [Coordinator]

gfsh>connect
Already connected to: DESKTOP-EMRTT29.hitronhub.home[1099]

gfsh>describe member --name=locate
Name        : locate
Id          : 192.168.0.82(locate:20936:locator)<ec><v0>:41000
Host        : DESKTOP-EMRTT29.hitronhub.home
Regions     :
PID         : 20936
Groups      :
Used Heap   : 259M
Max Heap    : 1988M
Working Dir : C:\Users\Milin\locate
Log file    : C:\Users\Milin\locate\locate.log
Locators    : 192.168.0.82[10334]

gfsh>start server --name=serverA --server-port=41101 --locators=locate
Starting a Geode Server in C:\Users\Milin\serverA...
.
Server in C:\Users\Milin\serverA on 192.168.0.82[41101] as serverA is currently online.
Process ID: 20920
Uptime: 36 minutes 6 seconds
Geode Version: 1.11.0
Java Version: 13.0.2
Log File: C:\Users\Milin\serverA\serverA.log
JVM Arguments: -Dgemfire.start-dev-rest-api=false -Dgemfire.use-cluster-configuration=true -XX:OnOutOfMemoryError=taskkill /F /PID %p -Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true -Dsun.rmi.dgc.server.gcInterval=9223372036854775806
Class-Path: C:\apache-geode-1.11.0\lib\geode-core-1.11.0.jar;C:\apache-geode-1.11.0\lib\geode-dependencies.jar

gfsh>list members
Member Count : 1

 Name  | Id
------ | --------------------------------------------------------------
locate | 192.168.0.82(locate:20936:locator)<ec><v0>:41000 [Coordinator]

gfsh>start server --name=serverA --server-port=41101 --locators=192.168.0.82[10334]
Starting a Geode Server in C:\Users\Milin\serverA...
.
Server in C:\Users\Milin\serverA on 192.168.0.82[41101] as serverA is currently online.
Process ID: 20920
Uptime: 36 minutes 27 seconds
Geode Version: 1.11.0
Java Version: 13.0.2
Log File: C:\Users\Milin\serverA\serverA.log
JVM Arguments: -Dgemfire.start-dev-rest-api=false -Dgemfire.use-cluster-configuration=true -XX:OnOutOfMemoryError=taskkill /F /PID %p -Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true -Dsun.rmi.dgc.server.gcInterval=9223372036854775806
Class-Path: C:\apache-geode-1.11.0\lib\geode-core-1.11.0.jar;C:\apache-geode-1.11.0\lib\geode-dependencies.jar

gfsh>list members
Member Count : 1

 Name  | Id
------ | --------------------------------------------------------------
locate | 192.168.0.82(locate:20936:locator)<ec><v0>:41000 [Coordinator]

gfsh>start server --name=serverB --server-port=41102 --locators=192.168.0.82[10334]
Starting a Geode Server in C:\Users\Milin\serverB...
.
Server in C:\Users\Milin\serverB on DESKTOP-EMRTT29.hitronhub.home[41102] as serverB is currently online.
Process ID: 8908
Uptime: 36 minutes 42 seconds
Geode Version: 1.11.0
Java Version: 13.0.2
Log File: C:\Users\Milin\serverB\serverB.log
JVM Arguments: -Dgemfire.start-dev-rest-api=false -Dgemfire.use-cluster-configuration=true -XX:OnOutOfMemoryError=taskkill /F /PID %p -Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true -Dsun.rmi.dgc.server.gcInterval=9223372036854775806
Class-Path: C:\apache-geode-1.11.0\lib\geode-core-1.11.0.jar;C:\apache-geode-1.11.0\lib\geode-dependencies.jar

gfsh>list members
Member Count : 1

 Name  | Id
------ | --------------------------------------------------------------
locate | 192.168.0.82(locate:20936:locator)<ec><v0>:41000 [Coordinator]

gfsh>start server --name=serverC --server-port=41103 --locators=192.168.0.82[10334]
Starting a Geode Server in C:\Users\Milin\serverC...
.
Server in C:\Users\Milin\serverC on DESKTOP-EMRTT29.hitronhub.home[41103] as serverC is currently online.
Process ID: 5940
Uptime: 36 minutes 44 seconds
Geode Version: 1.11.0
Java Version: 13.0.2
Log File: C:\Users\Milin\serverC\serverC.log
JVM Arguments: -Dgemfire.start-dev-rest-api=false -Dgemfire.use-cluster-configuration=true -XX:OnOutOfMemoryError=taskkill /F /PID %p -Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true -Dsun.rmi.dgc.server.gcInterval=9223372036854775806
Class-Path: C:\apache-geode-1.11.0\lib\geode-core-1.11.0.jar;C:\apache-geode-1.11.0\lib\geode-dependencies.jar

gfsh>start server --name=serverD --server-port=41104 --locators=192.168.0.82[10334]
Starting a Geode Server in C:\Users\Milin\serverD...
.
Server in C:\Users\Milin\serverD on DESKTOP-EMRTT29.hitronhub.home[41104] as serverD is currently online.
Process ID: 16548
Uptime: 36 minutes 44 seconds
Geode Version: 1.11.0
Java Version: 13.0.2
Log File: C:\Users\Milin\serverD\serverD.log
JVM Arguments: -Dgemfire.start-dev-rest-api=false -Dgemfire.use-cluster-configuration=true -XX:OnOutOfMemoryError=taskkill /F /PID %p -Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true -Dsun.rmi.dgc.server.gcInterval=9223372036854775806
Class-Path: C:\apache-geode-1.11.0\lib\geode-core-1.11.0.jar;C:\apache-geode-1.11.0\lib\geode-dependencies.jar

我无法理解为什么会这样。另外,我从来没有一次能够一次正确地获得此启动配置。有时,JMX Manager无法连接,有时定位器也无法启动,仅是我在一个项目上工作,这浪费了我很多时间,而且我无法花时间在应用程序部分(我正在用Java进行开发。

随时提供建议

gemfire geode gfsh
1个回答
0
投票

这应该是开箱即用的,这里发生了一些奇怪的事情……您可以确保服务器完全停止并且没有任何僵尸进程吗? [before再次启动集群吗?。

我只是想知道是否在启动定位器之前就已经启动了服务器,基本上是因为start server命令的输出表明服务器已经运行了一段时间...

Uptime: 20 minutes 12 seconds Uptime: 36 minutes 44 seconds

最诚挚的问候。
© www.soinside.com 2019 - 2024. All rights reserved.