Splunk® Enterprise

Admin Manual

Download manual as PDF

Splunk Enterprise version 6.x is no longer supported as of October 23, 2019. See the Splunk Software Support Policy for details. For information about upgrading to a supported version, see How to upgrade Splunk Enterprise.
This documentation does not apply to the most recent version of Splunk. Click here for the latest version.
Download topic as PDF

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.

  1. Stop the search head that has the stale KV store member.
  2. Run the command splunk clean kvstore --local.
  3. Restart the search head.
Last modified on 06 October, 2016
PREVIOUS
About the app key value store 		  NEXT
Back up KV Store

This documentation applies to the following versions of Splunk® Enterprise: 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

Was this documentation topic helpful?

Enter your email address, and someone from the documentation team will respond to you:

Please provide your comments here. Ask a question or make a suggestion.

You must be logged into splunk.com in order to post comments. Log in now.

Please try to keep this discussion focused on the content covered in this documentation topic. If you have a more general question about Splunk functionality or are experiencing a difficulty with Splunk, consider posting a question to Splunkbase Answers.

0 out of 1000 Characters