Index Administration
-
Indexes can be easily managed from the Studio or via maintenance operations in the Client API.
-
The following actions can be applied:
Pause & resume index
- An index can be paused (and resumed).
- See pause index & resume index for detailed information.
- Operation scope: Single node.
Pause & resume indexing
- You can pause (and resume) indexing of ALL indexes.
- See pause indexing & resume indexing for detailed information.
- Operation scope: Single node.
Disable & enable index
- An index can be disabled (and enabled), this is a persistent operation.
- See disable index & enable index for detailed information.
- Operation scope: Single node, or all database-group nodes.
Disable & enable indexing
- Indexing can be disabled (and enabled) for ALL indexes, this is a persistent operation.
- This is done from the database list view in the Studio.
- Operation scope: All database-group nodes.
Reset index
- Resetting an index will force re-indexing of all documents that match the index definition.
An index usually needs to be reset once it reached its error quota and is in an Error state. - See reset index for detailed information.
- Operation scope: Single node.
Delete index
- An index can be deleted from the database.
- See delete index for detailed information.
- Operation scope: All database-group nodes.
Set index lock mode
- The lock mode controls whether modifications to the index definition are applied (static indexes only).
- See set index lock for detailed information.
- Operation scope: All database-group nodes.
Set index priority
- Each index has a dedicated thread that handles all the work for the index.
Setting the index priority will affect the thread priority at the operating system level. - See set index priority for detailed information.
- Operation scope: All database-group nodes.
Customize indexing configuration
-
There are many indexing configuration options available.
-
A configuration key with a "per-index" scope can be customized for a specific index,
overriding the server-wide and the database configuration values. -
The "per-index" configuration key can be set from:
- The configuration tab in the Edit Index view in the Studio.
- The index class constructor when defining an index.
- The index definition when sending a putIndexesOperation.
Expert configuration options:
- Server.IndexingAffinityMask - Control the affinity mask of indexing threads
- Server.NumberOfUnusedCoresByIndexes - Set the number of cores that won't be used by indexes