| Previous | Next |
| MSG_CI_MASTER_MERGE_REASON_EXTERNAL | MSG_CI_MASTER_MERGE_REASON_EXPECTED_DOCS |
MSG_CI_MASTER_MERGE_REASON_INDEX_LIMIT
MSG_CI_MASTER_MERGE_REASON_INDEX_LIMIT identifies an internal consolidation threshold. The catalog accumulated the maximum number of index components at the last level, so a master merge was started to consolidate them.
Treat the event as index-shape telemetry, not corruption
- Capture the index-count value supplied in the event and the catalog name.
- Compare frequency with indexing volume and merge completion time; sustained high ingest can naturally reach consolidation thresholds more often.
- Investigate only when merges cannot keep up, repeatedly abort, or are blocked by storage/resource errors.
Merge documentation describes the progression from word lists to shadow indexes and finally the master index. A component-count threshold is part of managing that accumulation. This reason code differs from low disk, explicit external requests, and expected-document thresholds, so do not collapse them into one “merge started” metric. If query performance or disk use is a concern, correlate those measurements with the full merge lifecycle and ingest rate.
Merging indexes · Full-text catalog components · Indexing process
Looking for a different code? Search another status or error code.