![]() ![]() $ splunk show kvstore-status -verbose |grep serverVersion Storage Engine hasn't been migrated to wireTiger. You will need requiredBytes=3107201024 bytes, but KV Store DB filesystem only has availableBytes=2286272512 Not enough space to upgrade KVStore (or backup). Migration is not required.Ĭreated version file path=/opt/splunk/var/run/splunk/kvstore_upgrade/versionFile40 Started standalone KVStore update, start_time=" 15:21:46". Starting migrate-kvstore.Ĭreated version file path=/opt/splunk/var/run/splunk/kvstore_upgrade/versionFile36 Lastly trying to understand the difference in the output of mongo versionsbetween kvstore-status command versus splunk cmd mongod -version, clearly pulling from two different places. ![]() The above link is for upgrading mongo in a cluster but not on a single instance, when looking at the options in splunk help kvstore I don't see anything for upgrading mongo either for a single instance, tried splunk start-shcluster-upgrade kvstore -version 4.2 -isDryRun true but of course it detected it wasn't a searchhead cluster. We have since fixed the disk space issue and were able to complete the engine migration to wiredTiger, however don't know how to bump up the mongo version to 4.2. During the Splunk Enterprise upgrade the migration to wiredTiger failed due to lack of disk space, the upgrade still continued and made the first hop of the mongo upgrade from version 3.6 to 4.0, it looks like after version 4.0 it tried to do the engine migration but couldn't because the lack of available disk space and therefore didn't do the last hop to version 4.2 of mongo. Looking to see how to upgrade mongo from 4.0 to 4.2 on a single instance deployment. Upgraded Splunk Enterprise version 9.0.0 from 8.2.5 ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |