Reindexing behavior depends on the triggering operation and your data source configuration, which determine how data is imported and how existing data is handled. Understanding these differences helps prevent data synchronization issues in production.
How it works
-
Operations that trigger reindexing: scheduled reindexing and offline change.
|
Application type |
Data source |
Scheduled reindexing |
Offline change |
|
High-Performance Search Edition |
RDS/PolarDB |
Full import from RDS/PolarDB |
Full import from RDS/PolarDB |
|
RDS/PolarDB + incremental updates from DTS |
Full import from RDS/PolarDB + incremental updates from DTS |
Full import from RDS/PolarDB + incremental updates from DTS |
|
|
Full import from MaxCompute + incremental updates via API |
Full import from MaxCompute |
Full import from MaxCompute + incremental data from the API during reindexing |
|
|
No data source |
(Not supported) |
(Not supported) |
Reindexing operations
OpenSearch maintains a copy of your data, including data synchronized from external sources. Reindexing is required when you change the application schema or need a full data import. The following operations trigger reindexing:
-
Scheduled reindexing: Typically used for daily full data imports from data sources like MaxCompute.
-
Offline change: Triggers reindexing when you modify the application schema, index schema, or attribute schema.
Scheduled reindexing
Create a scheduled reindexing task to automatically rebuild your index once a day at a specified time.
-
Go to the OpenSearch console. In the top-left corner, select OpenSearch-High-Performance Search Edition. On the Application Management page, click Details for your application.
-
Click Reindex.
-
Select the execution time for the scheduled reindexing task. The minimum frequency is once per day.
In the scheduled task configuration panel, use the day-of-week button group (Monday to Sunday) to select the execution days. You can also select Automatically update data. After configuring these settings, click Modify to save them.
-
An application can have at most two versions: an online version and an offline version. If two versions already exist, scheduled reindexing automatically deletes the offline version. For manual reindexing, you must delete the offline version yourself.
-
When a scheduled reindexing task is complete, the new offline version automatically becomes the online version. The previous online version is automatically deleted after 8 to 16 hours.
Reindexing process and progress
The reindexing process consists of the following stages: data import > data processing > index building.
After data is imported from the data source, the system processes it and sends it to the build service for index building. Each full import build cycle takes about 30 minutes, so even a small number of documents may take some time to complete. The reindexing progress in the console is updated in stages.
-
After an offline change creates a new offline version, the console displays both the online and offline versions on the application details page.
-
When both an online and offline version exist, only the online version serves search requests. By default, API calls to the application name target the online version.
-
If both an online and an offline version exist, the offline change and reindexing features are unavailable. In this case, you must reduce the application to a single version. Publish the version you want to keep, and then delete the unneeded offline version.
-
Deleting an application version is irreversible.