Add a SmartStore index
The process of adding a SmartStore index is similar to adding a non-SmartStore index. You create a new index stanza in
indexes.conf and configure path information and other settings. See Create custom indexes.
As with all
indexes.conf settings, use the configuration bundle method when adding an index to the peer nodes on an indexer cluster.
Note the following:
- SmartStore-related settings in
indexes.confare usually configured at the global level, not at the individual index level. In that case, it is unlikely that you will need to specify those settings when adding a new index. However, if you are using multiple remote volumes or if you have a mix of SmartStore and non-SmartStore indexes, you must specify the SmartStore settings at the index level.
- If the SmartStore settings are configured globally, then a new index stanza usually needs only the
- You must specify a value for
coldPath, even though SmartStore does not use the
maxDataSize = auto(the default value, which is 750MB).
- See SmartStore settings in indexes.conf for a list of relevant SmartStore settings.
For example, assume that you have already set all SmartStore-related configurations at the global level. Then, to configure a new index called "cs_index", just add the following stanza to
[cs_index] homePath = $SPLUNK_DB/cs_index/db thawedPath = $SPLUNK_DB/cs_index/thaweddb coldPath = $SPLUNK_DB/cs_index/colddb
In the case of indexer clusters, all index stanzas must either include the setting
repFactor = auto or inherit the setting from the global level .
Configure data retention for SmartStore indexes
This documentation applies to the following versions of Splunk® Enterprise: 7.2.0, 7.2.1, 7.2.2, 7.2.3, 7.2.4, 7.2.5, 7.2.6, 7.2.7, 7.2.8, 7.2.9, 7.2.10
Feedback submitted, thanks!