When you perform operations on an Alibaba Cloud Elasticsearch (ES) instance—such as changing the cluster configuration, restarting the instance, or performing a scale-out or scale-in—you can track the progress and status on the Change Records page. This page also lists the instance's change history for the past 30 days.
Procedure
Log on to the Alibaba Cloud Elasticsearch console.
In the left navigation menu, choose Elasticsearch Clusters.
Navigate to the target cluster.
In the top navigation bar, select the resource group to which the cluster belongs and the region where the cluster resides.
On the Elasticsearch Clusters page, find the cluster and click its ID.
In the left-side navigation pane, click Change Records to view the progress, status, and details of instance changes within the selected time period.
NoteBy default, the system displays change records for the past 24 hours. You can also view records for the past 7 days, the past 30 days, or a custom time range. Change history is stored for a maximum of 30 days.
Parameter
Description
Change Start Time
The time a user triggered the instance change.
Change Type
The type of user-triggered change, such as an instance creation, restart, or cluster configuration change.
Changed By
The ID of the Alibaba Cloud account or RAM user who triggered the change.
Change Status
In Progress: The change is in progress. Please wait.
Complete: The change is complete.
Paused: If you did not manually pause the change, you can click View Logs to view the reason for the pause.
Change End Time
Only changes with a Complete status have an end time.
Actions
Show Details: Click Show Details to open the Change Details panel, where you can view basic information, the change type, and a before-and-after comparison.
NoteSome parameters in the Change Details panel are displayed in a low-level format. For more information, refer to the documentation for the specific change type. For example, for changes to YML parameters, see Configure YML parameters.
View Logs: Click View Logs to view the instance's operation logs on the Log Search page. For more information, see Query logs.
Related documents
If your cluster is not responding and requires an emergency recovery, restart the instance with a higher concurrency setting. For more information, see Restart a cluster or node.