Instruct SnappyData members to stop waiting for a disk store to become available.
./bin/snappy revoke-missing-disk-store <disk-store-id> <-locators=<addresses>> [-bind-address=<address>] [-<prop-name>=<prop-value>]*
The table describes options and arguments for snappy revoke-missing-disk-store. If no multicast or locator options are specified on the command-line, the command uses the gemfirexd.properties file (if available) to determine the distributed system to which it should connect.
|-disk-store-id||(Required.) Specifies the unique ID of the disk store to revoke.|
|-locators||List of locators used to discover members of the distributed system. Supply all locators as comma-separated host:port values. The port is the
|-bind-address||The address to which this peer binds for receiving peer-to-peer messages. By default SnappyData uses the hostname, or localhost if the hostname points to a local loopback address.|
|-prop-name||Any other SnappyData distributed system property.|
This command first lists the missing disk store:
./bin/snappy list-missing-disk-stores -locators=localhost:10334 Connecting to distributed system: -locators=localhost:10334 1f811502-f126-4ce4-9839-9549335b734d [curwen.local:/Users/user1/snappydata/rowstore/SnappyData_RowStore_13_bNNNNN_platform/server2/./datadictionary]
snappy revokes the missing disk store if more recent data is available:
./bin/snappy revoke-missing-disk-store 1f811502-f126-4ce4-9839-9549335b734d -locators=localhost:10334 Connecting to distributed system: -locators=localhost:10334 revocation was successful and no disk stores are now missing
snappy verifies that no disk stores are missing:
./bin/snappy list-missing-disk-stores -locators=localhost:10334 Connecting to distributed system: -locators=localhost:10334 The distributed system did not have any missing disk stores