...

...

...

...

...

...

...

...

...

...

Table of Contents

Steps:

Create a namespace with bugfest dataset

...

As indexation is a heavy process that has a 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.

You could perform this operation via Rancher in the Deployment section

Modules: 

• mod-search (1 → 4)
• mod-inventory-storage (1 → 2)

Pic. 2 Example "Backend module scale up"

...

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: 

{
  "recreateIndex": true,
  "resourceName": "authority"
}

...

Adjust indices settings

An additional configuration for improving indexation duration and stability is switching-off replication and refresh interval for indices.

On the Rancher environment, you could easily do this with OpenSearch Dashboars in "Dev Tools" section.

You need to perform a PUT request to modify setting of each newly created indices.

Indices:

• instance
• instance_subject
• contributor

// Request
PUT /folio-testing-sprint_instance_fs09000000/_settings
{
    "index": {
        "number_of_replicas": "1",
        "refresh_interval": "1s"
    }
}

// Response
{
	acknowledged: true
}

Wait for complete

Now, just wait for index completion.

It is 3 possible ways how to track index progress and completeness:

• mod-search and mod-inventory-storage logs
• Kafka messages number for topics mentioned above
• OpenSearch "Indexing Data Rate" in AWS Managment Console

Scale-down backend modules

After successfully completed of indexation, do not forget to scale down backend modules in Rancher

Modules: 

• mod-search (4 → 1) (or 4 → 2 for namespaces with HA mode)
• mod-inventory-storage (2 → 1) (or not scale down for namespaces with HA mode)

Scale-down OpenSearch