Resync the KV store
When a KV store member fails to transform its data with all of the write operations, then the KV store member might be stale. To resolve this issue, you must resynchronize the member.
Identify a stale KV store member
Check the REST introspection
/serverstatus endpoint to identify a stale KV store member. You can use cURL to make a GET request for the endpoint.
curl -k -u user:pass https://<host>:<mPort>/services/server/introspection/kvstore/serverstatus
If the endpoint fails to return introspection data, then the member is stale.
For more information about the REST API, see Basic Concepts in the REST API User Manual.
For more information about introspection endpoints, see Introspection endpoint descriptions in the REST API Reference Manual.
Resync stale KV store members
If more than half of the members are stale, then recreate the cluster. See Back up KV store.
If fewer than half of the members are stale, resync each KV store member individually.
- Stop the search head that has the stale KV store member.
- Run the command
splunk clean kvstore --local.
- Restart the search head.
About the app key value store
Back up KV Store
This documentation applies to the following versions of Splunk® Enterprise: 6.2.1, 6.2.2, 6.2.3, 6.2.4, 6.2.5, 6.2.6, 6.2.7, 6.2.8, 6.2.9, 6.2.10, 6.2.11, 6.2.12, 6.2.13, 6.2.14, 6.2.15, 6.3.0, 6.3.1, 6.3.2, 6.3.3, 6.3.4, 6.3.5, 6.3.6, 6.3.7, 6.3.8, 6.3.9, 6.3.10, 6.3.11, 6.3.12, 6.3.13, 6.3.14, 6.4.0, 6.4.1, 6.4.2, 6.4.3, 6.4.4, 6.4.5, 6.4.6, 6.4.7, 6.4.8, 6.4.9, 6.4.10, 6.4.11