Skip to Navigation
Resume Indexing Operation
-
After indexing has been paused using StopIndexingOperation,
useStartIndexingOperationto resume indexing for ALL indexes in the database.
Calling
StartIndexingOperationon a single index will have no effect. -
When resuming indexing from the client:
Indexing is resumed on the preferred node only, and Not on all the database-group nodes. -
When resuming indexing from the Studio database list view:
Indexing is resumed on the local node the browser is opened on, even if it is Not the preferred node. -
In this page:
Resume indexing example
// Define the resume indexing operation
const resumeIndexingOp = new StartIndexingOperation();
// Execute the operation by passing it to maintenance.send
await store.maintenance.send(resumeIndexingOp);
// At this point,
// you can be sure that all indexes on the preferred node are 'running'
// Can verify indexing status on the preferred node by sending GetIndexingStatusOperation
const indexingStatus = await store.maintenance.send(new GetIndexingStatusOperation());
assert.strictEqual(indexingStatus.status, "Running");
Syntax
// class name has "Start", but this is ok, this is the "Resume" operation
const resumeIndexingOp = new StartIndexingOperation();
Related Articles