1.0

Table Of Contents
Why Disk Stores Go Missing
Disk stores usually go missing because their member fails to start. The member can fail to start for a number of
reasons, including:
Disk store le corruption. You can check on this by validating the disk store.
Incorrect distributed system conguration for the member
Network partitioning
Drive failure
Note: The disk store directories listed for missing disk stores may not be the directories you have currently
congured for the member. The list is retrieved from the other running membersthe ones who are
reporting the missing member. They have information from the last time the missing disk store was online.
If you move your les and change the members conguration, these directory locations will be stale.
List Missing Disk Stores
The sqlf list-missing-disk-stores command lists all disk stores with most recent data that are
being waited on by other members.
For replicated tables, this command only lists missing members that are preventing other members from starting
up. For partitioned tables, this command also lists any ofine data stores, even when other data stores for the
table are online, because their ofine status may be causing PartitionOfflineExceptions in cache
operations or preventing the system from satisfying redundancy.
Example:
sqlf list-missing-disk-stores
Connecting to distributed system: mcast=/239.192.81.2:12348
DiskStore at straw.gemstone.com
/export/straw3/users/jpearson/testGemFire/hostB/DS1
Note: Make sure this sqlf call can nd a sqlfire.properties le to locate the distributed system.
Or, specify the multicast port or locator properties to connect to the cluster (for example, -mcast-port=
port_number).
Revoke Missing Disk Stores
This section applies to disk stores for which both of the following are true:
Disk stores that have the most recent copy of data for one or more tables or table buckets.
Disk stores that are unrecoverable, such as when you have deleted them, or their les are corrupted or on a
disk that has had a catastrophic failure.
When you cannot bring the latest persisted copy online, use the revoke command to tell the other members to
stop waiting for it. Once the store is revoked, the system nds the remaining most recent copy of data and uses
that.
Note: Once revoked, a disk store cannot be reintroduced into the system.
Use the sqlf list-missing-disk-stores command to identify the disk store you need to revoke. The
revoke command takes the host and directory in input, as listed by that command.
Example:
sqlf list-missing-disk-stores
Connecting to distributed system: mcast=/239.192.81.2:12348
DiskStore at straw.gemstone.com
vFabric SQLFire User's Guide86
Managing Your Data in vFabric SQLFire