Troubleshoot backup and log issues

Available in Classic and VPC

You might run into the following problems when using Search Engine Service. Find out causes and possible solutions.

Snapshot creation failed

Unable to create the snapshot.

Cause

You cannot create a snapshot in these cases:

• Another snapshot is being created or deleted.
• The API credentials belong to a sub account that lacks the required Object Storage permissions.

Snapshots may fail to be created properly in these situations:

• Cluster usage is high (heavy data ingestion or many search queries).
• The cluster is being restored, or shards are in the initializing state.
• The snapshot repository contains too much data, causing timeouts.
• Two or more clusters are creating snapshots to the same snapshot repository (same bucket name and base_path).
• You disable the API key during snapshot creation.
• You delete the bucket or change its access control during snapshot creation.
• When you remove the Object Storage plugin (s3-repository) or delete/change API keys (s3.client.default.access_key, s3.client.default.secret_key).

Solution

• Check whether another snapshot operation is in progress or being deleted.
• Verify that the sub account has Object Storage permissions.
• Try creating the snapshot during off‑peak hours.
• If the snapshot repository contains a very large amount of data, create the snapshot by calling the API directly.
  • See Create a snapshot via the Elasticsearch and OpenSearch APIs (VPC) or Create a snapshot via the Elasticsearch API (Classic).
• Do not change API credentials, the Object Storage plugin, or bucket settings while a snapshot is being created.
• If you have more than 300 snapshots, delete older snapshots.

Cannot deliver logs

Logs cannot be delivered for a specific time window.

Cause

It appears the ELASTICSEARCH_TEMPORARY_TIMEOUT error is occurring.
If you send too much bulk data at once, an error can occur.

Solution

• You can check Search Engine Service error logs in Cloud Log Analytics. In the NAVER Cloud Platform console, open Cloud Log Analytics to view the logs.
• Split the data into smaller batches or adjust the transfer rate.

Compliance settings not applied

You changed Compliance settings in OpenSearch Dashboards, but the change does not appear in the logs and is not applied.

Cause

All logs are stored in /home/nes/elasticsearch-logs first, then collected into Cloud Log Analytics. Audit logs are stored in /home/nes/elasticsearch-logs/{cluster-name}-audit.json.

Solution

Check whether your configured logs are stored in /home/nes/elasticsearch-logs or /home/nes/elasticsearch-logs/{cluster-name}-audit.json.