Tencent Cloud Elasticsearch Service (ES) provides the scenario-based template configuration feature. You can select an appropriate scenario-based configuration index template based on your business needs to optimize the cluster performance in the corresponding scenario and reduce the performance problems caused by the use of an incorrect index template. General, search, and log scenarios are supported for such a template. This document describes how to select a template and the template parameters.
Before using a scenario-based index template, please pay attention to the following:
default@templatethat has been optimized for most scenarios in your ES cluster. You can run the
GET _template/default@templatecommand in Dev Tools of Kibana to view the template.
scene@template. You can run the
GET _template/scene@templatecommand in Dev Tools of Kibana to view the template.
Enter the ES purchase page and select an initial scenario configuration template in the scenario-based configuration section. After the ES cluster is successfully purchased, the corresponding index configuration will be applied to it.
The scenario-based index template parameters are detailed as below:
|order||Template priority. The higher the value, the higher the priority|
|index_patterns||Index mode matched by index template. Wildcard is supported, which is
|index.refresh_interval||Index refreshing interval. Once indexed, a document can be queried only after the specified interval elapses. If you have a high requirement for query real-timeliness, you can slightly decrease the value; however, if the value is too small, the write performance will be affected|
|index.translog.durability||Translog data storage method.
|index.translog.sync_interval||Async refreshing interval which takes effect when the translog storage method is