Before you dig into reading this guide, have you tried asking OpsGPT what this log means? You’ll receive a customized analysis of your log.
Try OpsGPT now for step-by-step guidance and tailored insights into your OpenSearch operation.
Briefly, this error occurs when OpenSearch takes too long to update the mapping of an index, exceeding the set timeout limit. This could be due to heavy indexing load, slow network, or insufficient resources. To resolve this, you can increase the timeout limit, reduce the indexing load by splitting it into smaller tasks, optimize your network speed, or allocate more resources to OpenSearch. Additionally, ensure that your cluster is healthy and not suffering from any underlying issues that could slow down operations.
For a complete solution to your to your search operation, try for free AutoOps for Elasticsearch & OpenSearch . With AutoOps and Opster’s proactive support, you don’t have to worry about your search operation – we take charge of it. Get improved performance & stability with less hardware.
This guide will help you check for common problems that cause the log ” timed out waiting for mapping updates ” + “(timeout [” + timeout + “]) ” to appear. To understand the issues related to this log, read the explanation below about the following OpenSearch concepts: recovery, mapping, indices.
Quick links
Overview
Mapping is similar to database schemas that define the properties of each field in the index. These properties may contain the data type of each field and how fields are going to be tokenized and indexed. In addition, the mapping may also contain various advanced level properties for each field to define the options exposed by Lucene and OpenSearch. You can create a mapping of an index using the _mappings REST endpoint. The very first time OpenSearch finds a new field whose mapping is not pre-defined inside the index, it automatically tries to guess the data type and analyzer of that field and set its default value. For example, if you index an integer field without pre-defining the mapping, OpenSearch sets the mapping of that field as long.
Examples
Create an index with predefined mapping:
PUT /my_index?pretty
{
"settings": {
"number_of_shards": 1
},
"mappings": {
"properties": {
"name": {
"type": "text"
},
"age": {
"type": "integer"
}
}
}
}Create mapping in an existing index:
PUT /my_index/_mapping?pretty
{
"properties": {
"email": {
"type": "keyword"
}
}
}View the mapping of an existing index:
GET my_index/_mapping?pretty
View the mapping of an existing field:
GET /my_index/_mapping/field/name?pretty
Notes
- It is not possible to update the mapping of an existing field. If the mapping is set to the wrong type, re-creating the index with updated mapping and re-indexing is the only option available.
Common problems
- The most common problem in OpenSearch is incorrectly defined mapping which limits the functionality of the field. For example, if the data type of a string field is set as text, you cannot use that field for aggregations, sorting or exact match filters. Similarly, if a string field is dynamically indexed without predefined mapping, OpenSearch automatically creates two fields internally. One as a text type for full-text search and another as keyword type, which in most cases is a waste of space.
- The mapping of each index is part of the cluster state and is managed by master nodes. If the mapping is too big, meaning there are thousands of fields in the index, the cluster state grows too large to be handled and creates the issue of mapping explosion, resulting in the slowness of the cluster.
How to optimize your OpenSearch mapping to reduce costs
Watch the video below to learn how to save money on your deployment by optimizing your mapping.
Log Context
Log “timed out waiting for mapping updates ” + “(timeout [” + timeout + “])” class name is PeerRecoveryTargetService.java. We extracted the following from OpenSearch source code for those seeking an in-depth context :
@Override
public void onTimeout(TimeValue timeout) {
// note that we do not use a timeout (see comment above)
listener.onFailure(
new OpenSearchTimeoutException("timed out waiting for mapping updates " + "(timeout [" + timeout + "])")
);
}
});
};
final IndexMetadata indexMetadata = clusterService.state().metadata().index(request.shardId().getIndex());
