Start a System with Disk Stores

When you start a SQLFire cluster with disk stores, it is recommended that you start all members with persisted data at the same time.

Procedure
  1. Start members with persisted data at the same time.

    When members with persistent data boot, they determine which have the most recent table data, and they initialize their caches using that data. If you do not start persistent data stores in parallel, some members may hang while waiting for other members to start.

    The following example bash script starts 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; sqlf server start &
    ssh serverb "cd /my/directory; sqlf server start &
    
    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 any member startup hangs. If a disk store with the most recent table data does not come online, other members wait indefinitely rather than come online with stale data. Check for missing disk stores with the sqlf list-missing-disk-stores command. See Handling Missing Disk Stores.
    1. If no disk stores are missing, your peer initialization may be slow for some other reason. Check to see if other members are hanging or fail to start.
    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.
      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.