member stop command

The member stop command stops one or all of the members that are running on a node into which you are logged. The command does not wait for all of the processes to finish running.

Usage notes

Only members that are in the STARTED state are stopped.

If your installation has at least two catalog members, and you stop all of your catalog members, you must restart at least two catalog members before the data grid is available. If you stop all of your catalog members except one, the data grid is still available.

This command also stops the heartbeat process, which periodically checks whether members are still active. The heartbeat process stops when all members are stopped. The heartbeat process is started by the member start or the member start_service command.

You can also stop a member in the same manner as a member stop command with the Windows service controller if you started the member with the member start_service command.

Restriction: If stopping a member with the Windows service controller takes longer than 110 seconds to complete, the member and the server process are immediately stopped. This action is controlled by the Windows services policy.
Important: When multiple WebSphere eXtreme Scale container members are shut down concurrently, some containers may become overloaded with data, causing one or more container members to run out of memory and terminate ungracefully. If this occurs, the remaining WebSphere eXtreme Scale container members may hang during shutdown. To prevent this from occurring, see Problems and solutions for preventing WebSphere eXtreme Scale container from hanging during shutdown to follow this procedure during WebSphere eXtreme Scale container shut down.

Environment

  • Windows 2008
  • Linux®

Authorization

Administrative user

Syntax

execute member stop <member type> [--timeout <kill_timeout_in_seconds>]

Option descriptions

member type
One or all of the four member types:
  • catalog
  • container
  • operational
  • informational
  • all
--timeout kill_timeout_in_seconds
Optional: The kill_timeout_in_seconds parameter is the time, in seconds, before the member is immediately stopped and the server process for the member is stopped.

Examples

Example: Stopping a particular member.
This command stops the catalog member on a node:
execute member stop catalog
Example: Stopping a particular member with a timeout period before the member is immediately.
This command stops the catalog member on a node within a time period of 90 seconds before the member is immediately stopped and the server process for the member is stopped:
execute member stop catalog --timeout 90