You should follow certain order guidelines when starting your GemFire system.
Start server-distributed systems before you start their client applications. In each
distributed system, follow these guidelines for member startup:
- Start locators first. See Pivotal GemFire Locator Process
for examples of locator startup commands.
- Start cache servers before the rest
of your processes unless the implementation requires that other processes be
started ahead of them. Pivotal GemFire Servers for
examples of cache server startup commands.
- If your distributed system uses
both persistent replicated and non-persistent replicated regions, you should
start up all the persistent replicated members in parallel before starting
the non-persistent regions. This way, persistent members will not delay
their startup for other persistent members with later data.
- If you are running producer
processes and consumer or event listener processes, start the producers
first. This ensures the consumers and listeners receive all notifications
You can optionally override the default timeout period for shutting down
individual processes. This override setting must be specified during member startup.
See Option for System Member Shutdown Behavior
Starting Up After Losing Data on Disk
This information pertains to catastrophic loss of GemFire disk store files. If you lose disk
store files, your next startup may hang, waiting for the lost disk stores to come
back online. If your system hangs at startup, use the gfsh
to list missing disk stores and, if
needed, revoke missing disk stores so your system startup can complete. You must use
the Disk Store ID to revoke a disk store. These are the two commands:
Disk Store ID | Host | Directory
------------------------------------ | --------- | -------------------------------------
60399215-532b-406f-b81f-9b5bd8d1b55a | excalibur | /usr/local/gemfire/deploy/disk_store1
gfsh>revoke missing-disk-store --id=60399215-532b-406f-b81f-9b5bd8d1b55a
Note: This gfsh commands require that you are connected to the distributed system
via a JMX Manager node.