Post-upgrade to 10.2506.2

Attention: If you are upgrading from an earlier version to a higher or the latest version, ensure that you complete the post-upgrade steps for each intermediate release that are listed on the post-upgrade page. If a version is not listed on the page, it means there are no post-upgrade steps required for that release.

This post-upgrade applies only if you are using the Optimizer service. After updating the service image to 10.2506.2, complete the post-upgrade steps to reindex the otmz-properties.

Procedure

For the old index alias otmz-properties, set is_write_index to false.

POST /_aliases
{
  "actions": [
    {
      "add": {
        "index": "otmz-properties-000001",
        "alias": "otmz-properties",
        "is_write_index": false
      }
    }
  ]
}

Create a new index.
```
PUT /otmz-properties-000002
```

Start reindexing from old to new index.

POST /_reindex
{
  "source": {
    "index": "otmz-properties-000001"
  },
  "dest": {
    "index": "otmz-properties-000002"
  }
}

Compare the document counts to ensure that the count for old and new indexes match.
```
GET /otmz-properties-000001/_count
GET /otmz-properties-000002/_count
```

Run the following API to assign an alias for the new index and set is_write_index to true.

POST /_aliases
{
  "actions": [
    {
      "add": {
        "index": "otmz-properties-000002",
        "alias": "otmz-properties",
        "is_write_index": true
      }
    }
  ]
}

Delete the old index.
```
DELETE /otmz-properties-000001
```
Note: During reindexing, only the following API works, while the POST, PUT, and DELETE APIs do not function.
```
GET https://{hostname}/optimizer/{tenantid}/v1/configuration/businessSettings
```