#Splunk .conf pricing upgrade#
Upgrade to Splunk Enterprise 9.0 or higher.The KV store non-captain nodes are synced from the captain on a rolling basis, one node at a time, and the migration process does not automatically back up KV store data to a separate location. (Optional) Back up your KV store data before you begin the migration process.The time it takes to migrate the KV store storage engine is proportional to the total data in your KV store. Plan sufficient time for your upgrade and migration.Do not add new search heads while the migration is in progress.Ĭomplete the following steps to prepare your deployment before you migrate your storage engine:.
Migrate the KV store in a clustered deployment Verify that you have the latest version of the storage engine after upgrade with the following command:.Complete any prompts during your Splunk Enterprise upgrade.Single-instance deployments of Splunk Enterprise 9.0 and higher are automatically migrated to the WiredTiger storage engine and the latest version of MongoDB, server version 4.2, during the upgrade. Migrate the KV store in a single-instance deployment
Complete the steps associated with your deployment type.Īfter completing your migration to WiredTiger and server version 4.2, you can optionally remove the unsupported binary files for previous versions of MongoDB. If you have multiple KV store nodes across a search head cluster, then you have a clustered KV store deployment. If your single instance of the KV store is located on a search head, the cluster manager, or any indexer node, you have a single-instance KV store deployment. To migrate your KV store storage engine during your upgrade to Splunk Enterprise 9.0 or higher, first determine your deployment type. If you prefer to perform the WiredTiger migration and the upgrade to Splunk Enterprise at separate times, check the documentation for your current version of Splunk Enterprise to complete your migration before initiating your upgrade to Splunk Enterprise 9.0 or higher. Migrating your storage engine before or during upgrade to Splunk Enterprise 9.0 or higher is a best practice, but migrating immediately after upgrade is required.Īll Splunk Enterprise versions 8.1 and higher support WiredTiger, so you can consider migrating to WiredTiger before your upgrade to reduce downtime during the upgrade. Migrate to WiredTiger either before or during upgrade to Splunk Enterprise 9.0, and then upgrade to server version 4.2. Splunk Enterprise versions 9.0 and higher require the WiredTiger storage engine and server version 4.2, which significantly reduces the amount of storage you need and improves performance.
0 kommentar(er)
