LATEST VERSION: 8.2.5 - CHANGELOG
Pivotal GemFire® v8.2

Starting a System with Disk Stores

Starting a System with Disk Stores

Starting members with persisted data at the same time gives you the most efficient startup.

To start a system with disk stores:
  1. Start all members with persisted data first and at the same time. Exactly how you do this depends on your members.

    When you start members with persisted data in parallel, you get the most efficient system startup. While they are initializing their caches, the members determine which have the most recent region data, and initialize their caches from that.

    Note: For replicates, where you can define persistence only in some of the region's host members, start the persistent replicates before the non-persistent replicates to make sure the data is recovered from disk.
    This is an example bash script for starting members in parallel. The script waits for the startup to finish and exits with an error status if one of the jobs fails.
    #!/bin/bash
    ssh servera "cd /my/directory;  gfsh start server --name=servera &
    ssh serverb "cd /my/directory; gfsh start server --name=serverb &
    
    STATUS=0;
    for job in `jobs -p`
    do
    echo $job
    wait $job;
    JOB_STATUS=$?;
    test $STATUS -eq 0 && STATUS=$JOB_STATUS;
    done
    exit $STATUS;
  2. Respond to hangs on member startup. If a most recent disk store does not come online, your other members will wait indefinitely rather than come online with stale data. Check for missing disk stores with the gfsh show missing-disk-stores command. See Handling Missing Disk Stores.
    1. If no disk stores are missing, your cache initialization is slow for some other reason. Check the information on member hangs in Diagnosing System Problems.
    2. If disk stores are missing that you think should be there:
      1. Make sure you have started the member. Check the logs for any failure messages. See Logging.
      2. Make sure your disk store files are accessible. If you have moved your member or disk store files, you must update your disk store configuration to match.
    3. If disk stores are missing that you know are lost, because you have deleted them or their files are otherwise unavailable, revoke them so the startup can continue. See Handling Missing Disk Stores.