| Table of Contents |
|---|
Steps:
Create a namespace with bugfest dataset
...
As indexation is a heavy process with high CPU and memory resources consumptions, it is required (and strongly recommended) to scale up the shared OpenSearch AWS service.
r6g.xlarge → r6g.2xlarge
Scale-up backend modules
For better performance, please scale up backend modules.
...
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
Body:
| Code Block | ||
|---|---|---|
| ||
{
"recreateIndex": true,
"resourceName": "authority"
} |
...
You need to perform a PUT request to modify the setting of each newly created indices.
...
- mod-search and mod-inventory-storage logs
- Kafka messages number for topics mentioned above
- OpenSearch "Indexing Data Rate" in AWS Managment Console
| Info | ||
|---|---|---|
| ||
07.13.2023 and all previous runs "Indexing Data Rate" on the Rancher environment have the next pattern. So if you see something similar in AWS Management Console for OpenSearch service, then indexation goes well.
|
...
After the indexation process is finished, do not forget to scale down the shared OpenSearch AWS service
r6g.2xlarge → r6g.xlarge (If no other conditions/constraints)