| Table of Contents |
|---|
Steps:
Create a namespace with Bugfest dataset
...
If decided to do this on a topic level only - log.retention.ms should be changed because it has higher precedence over ..minutes and it's usually already set to some value.
Tune mod-search config(REQUIRED)
KAFKA_EVENTS_CONCURRENCY (default - 2) with higher value could increase instances reindex.
...
After completion of all pre-required steps, trigger index with POST Postman request.
URI: /search/index/inventory/reindex
Headers: X-Okapi-Tenant & X-Okapi-Token
items for resourceName: instance, authority, location
Body:
| Code Block | language | groovy
|---|
{
"recreateIndex": true,
"resourceName": "instance",
"indexSettings": {
"numberOfShards": 1,
"numberOfReplicas": 1
}
} |
| Info | ||
|---|---|---|
| ||
More information about index and requests you could find here: |
...
Scale-down backend modules(REQUIRED)
After the indexation process is finished, do not forget to scale down the backend modules in Rancher
...
Return previous value to log.retention property (usually 8 hours).
Tune mod-search config back(REQUIRED)
Return modified env variables to default values
An additional approach in case if reindex doesn't work properly (failing, stuck, etc...)
1. Recreate Kafka topics from KafkaUI
2. Remove existing indexes from OpenSearch
3. Send PUT and POST requests from OpenSearch to clone indexes, do it for all the necessary tenants,
select all the rows and send a request
In this example for tenant fs09000000
...