1) The simplest and fastest way to correct the replica node is to restore it from the master node. We will send you instructions for doing this later today.Here are directions for refreshing the data storage files (.jdb files) on a target node. NoSQL DB will automatically refresh the storage files from another node, after we manually stop the target node, delete its storage files, and finally restart it, as described below. Thanks to Linda Lee for these directions.
Find the directory containing the target Replication Node's files.
java -jar KVHOME/lib/kvstore.jar runadmin -host <host> -port <port>
In this example, rg1-rn3's storage is located in
kv-> show topology -verbose store=mystore numPartitions=100 sequence=108 dc=[dc1] name=MyDC repFactor=3 sn=[sn1] dc=dc1 localhost:13100 capacity=1 RUNNING [rg1-rn1] RUNNING c:/linda/work/smoke/KVRT1/dirB single-op avg latency=0.0 ms multi-op avg latency=0.67391676 ms sn=[sn2] dc=dc1 localhost:13200 capacity=1 RUNNING [rg1-rn2] RUNNING c:/linda/work/smoke/KVRT2/dirA No performance info available sn=[sn3] dc=dc1 localhost:13300 capacity=1 RUNNING [rg1-rn3] RUNNING c:/linda/work/smoke/KVRT3/dirA single-op avg latency=0.0 ms multi-op avg latency=0.53694165 ms shard=[rg1] num partitions=100 [rg1-rn1] sn=sn1 haPort=localhost:13111 [rg1-rn2] sn=sn2 haPort=localhost:13210 [rg1-rn3] sn=sn3 haPort=localhost:13310 partitions=1-100
Stop the target service using the stop-service command
In another command shell, remove the files for the target Replication Node
kv-> plan stop-service -service rg1-rn3 -wait
In the Admin CLI, restart the service
The service will restart, and will populate its missing files from one of the other two nodes in the shard. You can use the "verify" or the "show topology" command to check on he status of the store.
plan start-service -service rg1-rn3 -wait