The same message appears me today over one of the SHC members. To solve, I follow the recommendations over the member (I have 3 SH, the last one was the problematic). First of all, you need to backup the KVstore. Splunk service should be running over the SH to backup. Later, you need to restore the KVStore. Splunk service should be stopped before of the command execution. All of these commands should be executed over the affected member. If you have multiple members affected, you would execute it on each affected member, or in all SH if all are being affected with this replication error. Last Splunk version (8.2.4) recommends to move KVStore to a new technology. Currently, Splunk uses mmapv1 as Storage Engine, but it's recommended to move to wiredTiger. Follow the docs to migrate your KVStore to recommended engine: Migrate the KV store storage engine - Splunk Documentation
... View more
