| Previous | Next |
| hrNyi | MSG_CI_MASTER_MERGE_CANT_RESTART |
MSG_CI_MASTER_MERGE_CANT_START
MSG_CI_MASTER_MERGE_CANT_START is different from an abort after work has begun. The merge failed at the start boundary, and the nested error parameter is required to determine whether the blocker is disk space, catalog state, service initialization, or another resource.
Diagnose the start failure before forcing another merge
- Record the catalog and expanded error parameter from the event.
- Check whether another merge or catalog transition was already active and correlate with service startup/reset events.
- Avoid repeated force-merge calls until the underlying error is resolved; they can produce noise without changing the precondition.
A forced master merge is an explicit catalog administration operation, while normal merge scheduling can also trigger consolidation. In both cases the merge must initialize against the current catalog state. A start failure means there is no completed merge to evaluate and no checkpoint to resume. Compare this code with MSG_CI_MASTER_MERGE_ABORTED, which indicates work was paused after start.
Forcing a master merge · Merging indexes · Master merge checkpoints
Looking for a different code? Search another status or error code.