Resolve search issues in Collate — missing assets, count mismatches, and empty Explore results — by running the Search Indexing application to reindex your data.
Description — Maximum number of entities sent in a single batch during reindexing. Default: 100.Best Practice — Adjust based on system capabilities. A larger batch size improves throughput but may increase memory usage. Monitor performance and fine-tune accordingly.
Description — Maximum payload size in bytes per batch. Default: 104,857,600 bytes (100 MB).Best Practice — Ensure the payload size is within your system’s capacity. If memory issues or timeouts occur, reduce this value.
Description — Number of threads used to produce reindexing events. Default: 1.Best Practice — Increasing this improves throughput but may cause contention if set too high. Balance with system CPU and I/O capacity.
Description — Number of threads used to consume reindexing events. Default: 1.Best Practice — Keep in sync with producer threads. Increase when the queue fills up frequently.
Description — Internal queue size for reindexing operations. Default: 100.Best Practice — A larger queue handles processing spikes but requires more memory. Adjust based on expected load.
Description — Maximum number of simultaneous requests sent to the search index. Default: 100.Best Practice — Tune based on your indexing server’s capacity. Too many concurrent requests can overwhelm the server.
Description — Wait time in milliseconds before the first retry. Default: 1000 ms (1 second).Best Practice — Increase if failures occur frequently due to server overload or network issues.
Description — Maximum wait time in milliseconds between retries. Default: 10,000 ms (10 seconds).Best Practice — Align with your latency tolerance. A longer backoff reduces load during peak times but slows recovery.
Description — Entity types to include in the reindexing process. Defaults to All entities.Best Practice — When troubleshooting a specific entity type, select only that type to speed up the reindex and reduce system load.
Description — When enabled, drops the existing index and builds a new one from scratch.Best Practice — Enable only when you need a clean slate — such as after major data model changes or during migration. Leave disabled for routine reindexing to preserve the existing index.
Description — Language used when recreating indexes. Default: EN.Best Practice — Change only if your data assets are primarily in a language other than English. Changing the language recreates indexes with updated language-specific analyzers.
Description — When enabled, automatically adjusts performance settings based on cluster capabilities and entity count.Best Practice — Leave enabled unless you want manual control over performance parameters.
Description — When enabled, distributes the indexing workload across partitions for improved throughput.Best Practice — Enable on large datasets or multi-node clusters. On small single-node setups, the overhead may outweigh the benefit.
Description — Chunk size used when distributing indexing work across partitions. Default: 10,000.Best Practice — Use larger values for high-throughput environments. Reduce if individual partitions are causing memory pressure.
Description — Limits reindexing to time-series data within the specified number of days. Default: 0 (reindex all data).Best Practice — Set a positive value (e.g., 15) to limit reindexing to recent data. This significantly reduces reindexing time for large datasets.
Description — Number of replica shards for the live index. Default: 1.Best Practice — Use 1 for high availability on multi-node clusters; use 0 for single-node setups.
Description — How often new writes become searchable. Default: 1s.Best Practice — The default provides near-real-time search. Increase (e.g., 5s) to reduce overhead on write-heavy workloads.
Description — Controls when the translog is flushed to disk. Options: request or async.Best Practice — Use request for stronger durability. Switch to async only if you need higher write throughput and can tolerate the risk.
Description — How frequently the translog syncs when durability is set to async. Default: 5s.Best Practice — Keep low if durability is important. Increase to improve write performance when some data loss risk is acceptable.
Temporary settings applied during the bulk reindex write phase to maximize throughput. These automatically revert to Live Index Settings before the alias swap.
Description — Replica count during bulk write. Default: 0.Best Practice — Keep at 0 during reindex. Replicas are populated after the new index is promoted.
Description — How often the index is refreshed during bulk write. Default: -1 (disabled).Best Practice — Leave at -1. Disabling refresh dramatically speeds up indexing. The staged index is not searchable during this phase, so this is safe.
Description — Durability setting used during bulk write. Default: async.Best Practice — Using async improves write speed. Settings revert to live values before the index becomes searchable.
Description — How frequently the translog syncs during bulk indexing. Default: 30s.Best Practice — A longer sync interval reduces I/O overhead during the write phase.
Description — When enabled, forces a segment merge before the index goes live.Best Practice — Leave disabled for most reindexing runs. Enable only when optimizing the index for read performance, at the cost of additional reindex time.
