Resume Indexing Operation


  • After indexing has been paused using StopIndexingOperation,
    use StartIndexingOperation to resume indexing for ALL indexes in the database.

    Calling StartIndexingOperation on 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
var resumeIndexingOp = new StartIndexingOperation();

// Execute the operation by passing it to Maintenance.Send
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
var indexingStatus = store.Maintenance.Send(new GetIndexingStatusOperation());
Assert.Equal(IndexRunningStatus.Running, indexingStatus.Status);
// Define the resume indexing operation
var resumeIndexingOp = new StartIndexingOperation();

// Execute the operation by passing it to Maintenance.SendAsync
await store.Maintenance.SendAsync(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
var indexingStatus = await store.Maintenance.SendAsync(new GetIndexingStatusOperation());
Assert.Equal(IndexRunningStatus.Running, indexingStatus.Status);

Syntax

// class name has "Start", but this is ok, this is the "Resume" operation
public StartIndexingOperation()