Previous Next JavaScript must be enabled to correctly display this content

## Smoke Testing the System

There are several things you can do to ensure that your data store is up and fully functional. You verify your data store using the `verify configuration` command in the CLI.

1. The `verify configuration` command inspects all the components of the data store. It also checks whether all store services are available. For the available store services, the command also checks for any version or metadata mismatches. The command requires no parameters, and runs in verbose mode, by default. For example:

       kv-> verify configuration

   Output:

       Verify: starting verification of store mystore based upon topology sequence #2
       0 partitions and 1 storage nodes
       Time: 2024-04-05 10:41:15 UTC   Version: 24.1.11
       See <hostname>:$KVROOT/mystore/log/mystore_{0..N}.log for progress messages
       Verify: Shard Status: healthy: 0 writable-degraded: 0 read-only: 0 offline: 0 total: 0
       Verify: Admin Status: healthy
       Verify: Zone [name=Boston id=zn1 type=PRIMARY allowArbiters=false masterAffinity=false]
       RN Status: online: 0 read-only: 0 offline: 0
       Verify: == checking storage node sn1 ==
       Verify:         sn1: sn1 has 0 RepNodes and is under its capacity limit of 1
       Verify: Storage Node [sn1] on <hostname>: 5000
       Zone: [name=Boston id=zn1 type=PRIMARY allowArbiters=false masterAffinity=false]
       Status: RUNNING   Ver: 24.1.11 2024-04-05 21:25:44 UTC  Build id: 477e7f102ab4
       Edition: Enterprise    isMasterBalanced: unknown     serviceStartTime: 2024-04-05 10:37:28 UTC
       Verify:         Admin [admin1]   Status: RUNNING,MASTER  serviceStartTime: 2024-04-05 10:38:21 UTC
       stateChangeTime: 2024-04-05 10:38:21 UTC    availableStorageSize: 999 MB

       Verification complete, 0 violations, 1 note found.
       Verification note: [sn1]  sn1 has 0 RepNodes and is under its capacity limit of 1

   If the output shows all Storage Nodes and replication nodes as running without any errors, then the data store is configured well and all Storage Nodes are up and active.
2. Run the ping command as shown below:

       kv-> ping

   Output:

       Pinging components of store mystore based upon topology sequence #2
       0 partitions and 1 storage nodes
       Time: 2024-04-05 11:36:06 UTC   Version: 24.1.11
       Shard Status: healthy: 0 writable-degraded: 0 read-only: 0 offline: 0 total: 0
       Admin Status: healthy
       Zone [name=Boston id=zn1 type=PRIMARY allowArbiters=false masterAffinity=false]
       RN Status: online: 0 read-only: 0 offline: 0
       Storage Node [sn1] on <hostname>: 5000
       Zone: [name=Boston id=zn1 type=PRIMARY allowArbiters=false masterAffinity=false]
       Status: RUNNING   Ver: 24.1.11 2024-04-05 21:25:44 UTC  Build id: 477e7f102ab4
       Edition: Enterprise  isMasterBalanced: unknown serviceStartTime: 2024-04-05 10:37:28 UTC
       Admin [admin1]  Status: RUNNING,MASTER  serviceStartTime: 2024-04-05 10:38:21 UTC
       stateChangeTime: 2024-04-05 10:38:21 UTC availableStorageSize: 999 MB

   If the output shows all Storage Nodes and replication nodes as running without any errors, then the data store is configured well and all Storage Nodes are up and active.

If you run into installation problems or want to start over with a new data store, then on every Storage node in the data store:

1. Stop the Storage Node using:

       java -Xmx64m -Xms64m \
       -jar $KVHOME/lib/kvstore.jar stop -root $KVROOT

2. Remove the contents of the KVROOT directory:

       rm -rf $KVROOT

3. Start over with the steps described in Installation Configuration Parameters.