Installation

How to complete a KVStore migration?

ggvaca
Explorer

I have upgraded to Splunk 8.2.3 recently in a test environment. The last step in upgrading our slightly outdated environment is to migrate the KVStore. I don't understand the directions. What system are we going into "the server.conf in the $SPLUNK_HOME/etc/system/local/ directory." Is it in the Deployer? Cluster Master? Any of the search heads we have? If that file is edited in one system, how is it being pushed to the search heads? 

Also could we leave the variable storageEngineMigration=true in that file or does it have to stay as false when not migrating? 

Thank you!

@https://docs.splunk.com/Documentation/Splunk/8.2.3/Admin/MigrateKVstore

Labels (3)
Tags (1)
0 Karma
1 Solution

m_pham
Splunk Employee
Splunk Employee

I'm assuming you fall under this category in the documentation? -> https://docs.splunk.com/Documentation/Splunk/8.2.3/Admin/MigrateKVstore#Migrate_the_KV_store_after_a...

If so, it looks like you modify the "server.conf" on each of the search head members (step #1). Then just follow the other steps after that.

Probably doesn't need to be said but back up your KV store just in case...

https://docs.splunk.com/Documentation/Splunk/8.2.3/Admin/BackupKVstore

View solution in original post

ggvaca
Explorer

What about leaving the variable storageEngineMigration=true in the server.conf? We use Git to store and run our files and I wasn't sure if this was a one and done situation after we upgrade or if we are going to want to push out this file to every system? It seems like this is a one and done once we upgrade. 

0 Karma

m_pham
Splunk Employee
Splunk Employee

I don't see anything about changing it back to false, so it seems like a permanent configuration.

 

storageEngineMigration = <boolean> 
* Whether or not you can migrate the KV Store storage engine on this instance.
* Migrating the storage engine means changing the engine from 'mmap' to 
  the newer 'wiredTiger'.
* If you set this to "true", the instance lets you migrate the engine,
  depending on the following scenarios:
  * If this instance is standalone, you can migrate the engine during
    an upgrade by enabling this setting with a "true" value as part of 
    the upgrade process and answering affirmatively when that process 
    prompts you, or after an upgrade by using the
    'splunk migrate kvstore-storage-engine' CLI command.
  * If it is a part of a search head cluster, you can perform the migration using the
    '/services/shcluster/captain/kvmigrate/start' REST endpoint.
* If you set this to "false", you cannot migrate the storage engine.
* Default: false

https://docs.splunk.com/Documentation/Splunk/8.2.3/Admin/Serverconf

0 Karma

m_pham
Splunk Employee
Splunk Employee

I'm assuming you fall under this category in the documentation? -> https://docs.splunk.com/Documentation/Splunk/8.2.3/Admin/MigrateKVstore#Migrate_the_KV_store_after_a...

If so, it looks like you modify the "server.conf" on each of the search head members (step #1). Then just follow the other steps after that.

Probably doesn't need to be said but back up your KV store just in case...

https://docs.splunk.com/Documentation/Splunk/8.2.3/Admin/BackupKVstore

Get Updates on the Splunk Community!

Improve Your Security Posture

Watch NowImprove Your Security PostureCustomers are at the center of everything we do at Splunk and security ...

Maximize the Value from Microsoft Defender with Splunk

 Watch NowJoin Splunk and Sens Consulting for this Security Edition Tech TalkWho should attend:  Security ...

This Week's Community Digest - Splunk Community Happenings [6.27.22]

Get the latest news and updates from the Splunk Community here! News From Splunk Answers ✍️ Splunk Answers is ...