To upgrade OpenSearch, you need to install a new OpenSearch cluster in the target version. Next, the following procedure describes how to push data from one OpenSearch cluster to another after creating your scope from the CLM.

Launch of re-indexing

In this section, we will ask OpenSearch to populate an index from another remote index.

OpenSearch will first check the request and then return the identifier of an asynchronous task. To do this, run the following request on the target cluster, adapting it to the environments:

POST /_reindex?wait_for_completion=false
{
  "source": {
    "remote": {
      "host": "http://localhost:9200",
      "username": "user",
      "password": "password"
    },
    "index": "<scope>-flower-docs",
    "type": "document",
    "size": 100
  },
  "dest": {
    "index": "<scope>-flower-docs"
  }
}

Note: In this request, <scope> is the identifier of the FlowerDocs scope in lower case.

The response returned by OpenSearch is of the type:

{
    "task": "<nodeId>:<taskId>"
} 

Re-indexing status

As the re-indexing task is asynchronous, it is possible to know its status:

GET /_tasks/<nodeId>:<taskId>

Depending on the response returned, it is therefore possible to determine whether the re-indexing has been carried out successfully or whether it is still running.

• A completed flag indicates whether or not re-indexing has been completed
• The recovered task mentions a response or error object indicating whether the task was successfully completed
  

All re-indexing tasks can also be viewed with:

GET /_tasks?detailed=true&actions=*reindex