An index shard is a unique subset of an index. Splitting an index into multiple shards allows the index to grow to a very large size and still be able to service requests in reasonable amounts of time.
Index shards are distributed amongst the instances that run the Index service. Index requests, such as user queries, are sent concurrently to multiple index shards.
To edit your index shard configuration values, follow the procedures below.
Increasing the number of shards or changing the Index Protetction Level
- Navigate to the Workflow API in Swagger.
- Copy the JSON representation of the index.
- Select GET /indexes/{uuid}.
- Click Try it out.
- Enter the UUID of your index into the indexUUID field.
- In the Server response section, copy the Response body.
- Edit the index.
- Select PUT /indexes/{uuid}.
- Click Try it out.
- Enter the UUID of your index into the indexUUID field.
- In the Server response section, delete the provided Edit Value Model text and paste the response body copied from step 2.
- In the pasted text, edit either the desiredShardCount or desiredIndexProtectionLevel value.
- Click Execute to apply the updated JSON.
Enabling/disabling shard monitoring or changing the Shard Monitoring Time Limit
- Navigate to the Workflow API in Swagger.
- Copy the JSON representation of the index.
- Select GET /indexes/solrOptions.
- Click Try it out.
- Click Execute to view all of the Solr options set for your indexes.
- Copy the Response body.
- Edit the index.
- Select PUT /indexes/solrOptions.
- Click Try it out.
- In the Request body section, delete the provided Edit Value Model text and paste the response body copied from step 2.
- In the pasted text, edit either the ENABLEDISABLENAME or shardMonitoringTimeLimit value.
- Click Execute to apply the updated JSON.
Rebalancing the shards of an index
- Navigate to the Workflow API in Swagger.
- Select POST indexes/{uuid}/queueRebalanceShards.
- Click Try it out.
- Enter the UUID of your index in the Index ID field.
- Click Execute.