Starting Up Your System

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 vFabric GemFire Locator Process for examples of locator startup commands.
  • Start cacheservers before the rest of your processes unless the implementation requires that other processes be started ahead of them. vFabric GemFire cacheserver for examples of cacheserver startup commands.
  • 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 and updates.
  • If you have processes that persist data to disk, start them close together if you can, so that they can negotiate to determine which has the most up to data copy of each region.
Note: 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 for details.

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 gemfire command to list missing disk stores and, if needed, revoke missing disk stores so your system startup can complete. These are the two commands:
gemfire list-missing-disk-stores

gemfire revoke-missing-disk-store <address> <directory>
Note: This call requires a gemfire.properties file for the distributed system.