Choose the storage location for each index

You can configure SmartStore globally, using the same settings for all indexes, or you can configure SmartStore on a per-index basis. If you configure SmartStore on a per-index basis, you can have a mix of SmartStore and non-SmartStore indexes on the same indexer or indexer cluster. You can also specify different remote volumes for different SmartStore indexes.

The remote volume, defined in indexes.conf, points to the remote store where SmartStore stores warm buckets, such as a location on an S3 or GCS bucket.

To summarize, you can choose from these storage options:

• All indexes stored remotely, on a single volume.
• All indexes stored remotely, on multiple volumes.
• Some indexes stored locally, with others stored remotely on one or more remote volumes.

Even with a SmartStore index, some index data is temporarily stored locally, in the cache. However, except for hot buckets, the index's master copies of buckets are stored remotely. For the sake of simplicity, the list of storage options assumes the index's master copies when discussing storage volumes and does not consider data stored locally in the SmartStore cache.

Keep these limitations in mind:

• Each remote volume is limited to a single indexer cluster or standalone indexer. That is, each remote store holds buckets for only a single cluster or standalone indexer. From the configuration standpoint, the path setting within each remote volume stanza in indexes.conf must be unique to the cluster or indexer. For example, if indexes on one cluster use a particular remote volume, no index on any other cluster or standalone indexer can uses the same remote volume.
• Each SmartStore index is limited to a single remote volume. All warm buckets for that index must reside in the same remote store.
• Each indexer or indexer cluster is limited to a single remote storage type, such as S3 or GCS, across all indexes.
• All peer nodes on an indexer cluster must use the same SmartStore settings.