Alibaba Cloud Elasticsearch offers two editions: Standard Edition and Advanced Edition. The two editions support different cluster versions. This topic describes how to view the edition and version of an Elasticsearch cluster, compares the two editions, and compares the various versions.

View the edition and version of a cluster

You can view the edition and version of your cluster on the Basic Information page of the cluster in the Elasticsearch console. For more information, see View the basic information of a cluster.

Edition comparisons

Item Standard Edition Advanced Edition
Features
  • All the features provided by open source Elasticsearch are supported.
  • Multiple open source Elasticsearch versions are provided.
  • The AliES kernel is provided and is optimized in minor versions.
  • A variety of capabilities are provided to meet requirements for various scenarios.
  • The compute-storage separation architecture is used.
  • The features provided by open source Elasticsearch are supported, and the kernel is optimized for logging scenarios.
  • High write throughput is supported at low storage costs.
  • A shared storage mechanism is used to achieve auto scaling within seconds.
Scenarios All scenarios are supported, such as log analysis, searches, and data analysis. The following scenarios are supported:
  • Scenarios in which large amounts of logs need to be analyzed
  • Scenarios in which highly concurrent queries exist
User personas
  • Users who want to use Elasticsearch in multiple scenarios.
  • Users who have planned their resources.
  • Users who understand Elasticsearch, Logstash, and Kibana (ELK) and have the ability to optimize cluster performance in various scenarios.
  • Users who want to reduce the costs in logging scenarios.
  • Users who want to reduce the O&M costs caused by business fluctuations.
  • Users who have high requirements for write performance optimization.
Supported versions V5.5, V5.6, V6.3, V6.7, V6.8, V7.7, and V7.10 are supported. V6.7 and V7.10 are supported.
Billing mode You are charged based on the specifications, storage space, and number of nodes in your cluster. You are charged based on the specifications and number of nodes in your cluster, the storage space used by hot data, and the volume of data written to hosted indexes. For more information, see Elasticsearch billable items and Logstash billable items.

Version comparisons

Open source Elasticsearch version Alibaba Cloud Elasticsearch version Feature change
7.x V7.10
Alibaba Cloud Elasticsearch:
Open source Elasticsearch:
  • The compression of storage fields is improved, which reduces storage costs.
  • Event Query Language (EQL) is used to improve security.
  • The default value of search.max_buckets is changed from 10000 to 65535.
  • Queries that are not case-sensitive are supported. To implement such queries, you must set the case_insensitive parameter to true.

For more information about feature changes, see Breaking changes in 7.10.

V7.7 Open source Elasticsearch:
  • The default number of shards in the index template is changed from 5 to 1.
  • Mapping types are removed. You do not need to specify a mapping type when you define a mapping or an index template. For more information, see Removal of mapping types.
  • By default, a maximum of 10,000 documents can be returned for each request. If more than 10,000 matching documents exist, Elasticsearch returns only 10,000 matching documents. For more information, see track_total_hits 10000 default.
  • By default, a single data node can store a maximum of 1,000 shards. You can use the cluster.max_shards_per_node parameter to change this limit. For more information, see Cluster Shard Limit.
  • By default, a maximum of 500 scrolls can be performed. You can use the search.max_open_scroll_context parameter to change this limit. For more information, see Scroll Search Context.
  • The parent circuit breaker works based on the current memory usage. This is controlled by the indices.breaker.total.use_real_memory parameter. By default, the parent circuit breaker starts to work when the current memory usage reaches 95% of JVM heap memory usage. This indicates that Elasticsearch uses the maximum memory availability to avoid out of memory (OOM) issues. For more information, see Circuit Breaker.
  • The _all field is removed to improve search performance.
  • Intervals queries are supported. Elasticsearch searches for and returns documents based on the order and proximity of matching terms.
  • After the audit logging feature is enabled, audit events are persisted to <clustername>_audit.json in the file system of each node. The audit events cannot be stored in indexes. For more information, see Enabling audit logging.

For more information about feature changes, see Breaking changes in 7.0.

6.x V6.3, V6.7, and V6.8 Open source Elasticsearch:
  • An index can have only one type, and the _doc type is recommended.
  • The index lifecycle management (ILM) feature is introduced from V6.6.0 to reduce index O&M costs.
  • The historical data rollup feature is introduced to help summarize historical data.
  • Elasticsearch SQL, an X-Pack component, is supported in V6.3 and later. It enables SQL statements to be converted to domain-specific language (DSL) statements. This reduces costs for learning DSL.
  • The Composite, Parent, and Weighted Avg aggregation functions are supported.

For more information about feature changes, see Breaking changes in 6.0.

V6.7 Alibaba Cloud Elasticsearch:
  • Some features, such as pruning for time series indexes and slow query isolation, are introduced based on the AliES kernel to improve query performance.
  • The faster-bulk and gig plug-ins are provided in addition to the plug-ins provided by open source Elasticsearch. The two plug-ins are used to improve cluster stability.
  • The Advanced Monitoring and Alerting service is introduced. This service implements fine-grained monitoring and alerting, such as shard- or segment-level monitoring and alerting.
  • Upgrades from V6.3.2 to V6.7.0 are supported. For more information, see Upgrade the version of a cluster.
5.x V5.5 and V5.6 Open source Elasticsearch:
  • An index can have multiple types, and custom types are supported.
  • The STRING data type is replaced by the TEXT or KEYWORD data type.
  • The values of fields in indexes are changed from not_analyzed or no to true or false.
  • The DOUBLE data type is replaced by the FLOAT data type to reduce storage costs.
  • Java High Level REST Client is launched to replace Transport Client.

For more information about feature changes, see Breaking changes in 5.0.

Create an Elasticsearch cluster