| Previous | Next |
| MSG_CI_CORRUPT_INDEX_COMPONENT | MSG_CI_MASTER_MERGE_REASON_EXTERNAL |
MSG_CI_MASTER_MERGE_ABORTED_LOW_DISK
MSG_CI_MASTER_MERGE_ABORTED_LOW_DISK gives a specific resource cause for a merge pause. Index consolidation writes new persistent structures, so low free space can stop progress even while ordinary queries still return results from the existing catalog.
Measure free space on the actual catalog volume
- Record free and total bytes on the volume that stores the catalog, not only the system drive.
- Check whether temporary growth from shadow indexes or another workload consumed space during the merge window.
- After freeing space, follow the same catalog for a restart event instead of repeatedly forcing new merges.
Legacy Indexing Service documentation exposes several merge thresholds tied to shadow-index size and minimum free disk space, showing why merge behavior is storage-sensitive. The practical recovery is to restore sufficient capacity and confirm that the scheduled merge resumes. Deleting random indexed documents is not a direct fix unless it materially changes catalog/storage pressure. If the event recurs at predictable intervals, trend free space and catalog growth rather than treating each occurrence as unrelated.
Merge-related registry thresholds · Merging indexes · Master merge checkpoints
Looking for a different code? Search another status or error code.