LATEST VERSION: 8.1.0 - CHANGELOG
stop
stop
Stop gateway receivers, gateway senders, locators, and servers.
stop gateway-receiver
Stop the gateway receiver on a member or members.
Availability: Online. You must be connected in gfsh to a JMX Manager member to use this command.
Syntax:
stop gateway-receiver [--group=value(,value)*] [--member=value]
| Name | Description |
|---|---|
| --group | Group(s) of members on which to stop the Gateway Receiver. Use a comma-separated list for multiple member groups. |
| --member | Name/Id of the member on which to stop the Gateway Receiver. |
Example Commands:
stop gateway-receiver --member=receiver1-LN stop gateway-receiver --group=LN-Group1
Sample Output:
gfsh>stop gateway-receiver
Member | Result | Message
--------------------------- | -------| -----------------------------------------------------------------------
pc13(2266)<v6>:56852 | OK | GatewayReceiver is stopped on member pc13(2266)<v6>:56852
pc13(Manager:2242)<v5>:57631| Error | GatewayReceiver is not available on member pc13(Manager:2242)<v5>:57631
pc13(2275)<v7>:47480 | OK | GatewayReceiver is stopped on member pc13(2275)<v7>:47480
pc13(2293)<v8>:55472 | OK | GatewayReceiver is stopped on member pc13(2293)<v8>:55472
gfsh>stop gateway-receiver --member=pc13(2266)<v14>:36579
GatewayReceiver is stopped on member pc13(2266)<v14>:36579
gfsh>stop gateway-receiver --group=RG1
Member | Result | Message
-------------------- | -------| ----------------------------------------------------------
pc13(2275)<v23>:27484| OK | GatewayReceiver is stopped on member pc13(2275)<v23>:27484
pc13(2293)<v24>:55810| OK | GatewayReceiver is stopped on member pc13(2293)<v24>:55810
pc13(2266)<v22>:4522 | OK | GatewayReceiver is stopped on member pc13(2266)<v22>:4522
stop gateway-sender
Stop a gateway sender with a given id on a specified member or members of a specified member group.
CAUTION:
Use caution with the stop
gateway-sender command (or equivalent
GatewaySender.stop() API) on parallel gateway senders.
Instead of stopping an individual parallel gateway sender on a member,
Pivotal recommends shutting down the entire member to ensure that proper
failover of partition region events to other gateway sender members. Using
this command on an individual parallel gateway sender can occur in event
loss. See Stopping Gateway Senders for more details.
Availability: Online. You must be connected in gfsh to a JMX Manager member to use this command.
Syntax:
stop gateway-sender --id=value [--group=value(,value)*] [--member=value]
| Name | Description |
|---|---|
| --id | Required. ID of the Gateway Sender. |
| --group | Group(s) of members on which to stop the Gateway Sender. |
| --member | Name/Id of the member on which to stop the Gateway Sender. |
Example Commands:
stop gateway-sender --id=ln --member=server1
Sample Output:
gfsh>stop gateway-sender --id=ln Member | Result | Message ---------------------------- | ------ | ------------------------------------------------------------------------ pc13(5184)<v7>:41914 | OK | GatewaySender ln is stopped on member pc13(5184)<v7>:41914 pc13(5192)<v8>:25704 | OK | GatewaySender ln is stopped on member pc13(5192)<v8>:25704 pc13(5174)<v6>:53996 | OK | GatewaySender ln is stopped on member pc13(5174)<v6>:53996 pc13(Manager:5148)<v5>:64040 | Error | GatewaySender ln is not available on member pc13(Manager:5148)<v5>:64040 gfsh>stop gateway-sender --id=ln --member=pc13(5174)<v14>:17819 GatewaySender ln is stopped on member pc13(5174)<v14>:17819 gfsh>stop gateway-sender --id=ln --group=SenderGroup1 Member | Result | Message --------------------- | ------ | ----------------------------------------------------------- pc13(5174)<v18>:63332 | OK | GatewaySender ln is stopped on member pc13(5174)<v18>:63332 pc13(5184)<v19>:20055 | OK | GatewaySender ln is stopped on member pc13(5184)<v19>:20055 pc13(5192)<v20>:14622 | OK | GatewaySender ln is stopped on member pc13(5192)<v20>:14622
stop locator
Stop a locator.
Availability: Online or offline. If you want to stop a locator while you are offline, use the --dir or the --pid parameter.
Syntax:
stop locator [--name=value] [--host=value] [--port=value] [--pid=value] [--dir=value]
| Name | Description | Default Value |
|---|---|---|
| --name | The GemFire member name or id of the Locator to stop. You must be connected to the JMX Manager to use this option. Can be used to stop remote locators. See Using gfsh to Manage a Remote Cluster Over HTTP or HTTPS. | |
| --pid | The process id (PID) of the running Locator. | |
| --dir | Directory in which the Locator was started. | current directory |
Example Commands:
stop locator --name=locator1 stop locator --dir=locator1 stop locator --pid=6716
Sample Output:
gfsh>stop locator --pid=2401 Stopping Locator running in /home/stymon/gemfire/locator1 on ubuntu.local[10334] as locator1... Process ID: 2401 Log File: /home/stymon/gemfire/locator1/locator1.log .... No longer connected to ubuntu.local[1099]. gfsh>
stop server
Stop a GemFire cache server.
Availability: Online or offline. If you want to stop a cache server while you are offline, use the --dir or the --pid parameter.
Syntax:
stop server [--name=value] [--pid=value] [--dir=value]
| Name | Description | Default Value |
|---|---|---|
| --name | Name/Id of the GemFire Cache Server to stop. You must be connected to the JMX Manager to use this option. Can be used to stop remote servers. See Using gfsh to Manage a Remote Cluster Over HTTP or HTTPS. | |
| --pid | Process ID (PID) of the running GemFire Cache Server. | |
| --dir | Directory in which the GemFire Cache Server was started. | current directory |
Example Commands:
stop server --name=server1 stop server --dir=server1 stop server --pid=8540
Sample Output:
gfsh>stop server --pid=2726 Stopping Cache Server running in /home/stymon/gemfire/server1 on ubuntu.local[40404] as server1... Process ID: 2726 Log File: /home/stymon/gemfire/server1/server1.log ....