This topic describes how to perform minor version upgrades and provides information about the updates of each minor version.

Note
  • ApsaraDB for HBase continues to provide services during an upgrade. The system performs a rolling upgrade on the cluster. To minimize the negative impact on your workloads, all regions are moved to other servers before the RegionServer restarts. When an upgrade is being performed, your business may be interrupted, but the cluster remains available. You can perform minor version upgrades as needed.
  • The period of time that is required to upgrade a cluster varies based on the size of the cluster and the number of regions in the cluster. The larger the cluster, the longer the period of time that is required for an upgrade. In most cases, it takes less than 10 minutes to upgrade a cluster that contains two core nodes and 100 regions. It may take more than 1 hour to upgrade a cluster that has many nodes and more than 1,000 regions.

Procedure

  1. Log on to the ApsaraDB for HBase console.
  2. In the top navigation bar, select the region where the instance that you want to manage is deployed.
  3. On the Clusters page, click the ID of the instance.
  4. In the left-side navigation pane, click Database Connection.
  5. Click Upgrade Minor Version.

Version description

Version Category Description
2.2.15 Feature optimization Lindorm SQL is optimized to resolve the issues that cause table creation failures and access failures that are related to strong consistency tables. We recommend that you upgrade your cluster to this version or a later version.
2.2.12 Feature optimization
  • Compaction policies are optimized to improve efficiency.
  • The volume of data that is returned for scan operations is optimized.
2.2.11 New features
  • Lindorm SQL is supported.
  • High-performance native secondary indexes are supported.
2.2.10 Feature optimization The issue that request errors occur due to network jitter for cold data is fixed. We recommend that you upgrade your cluster to this version or a later version.
2.2.9 New features A feature that allows you to dynamically generate tokenizer configurations is added to SearchIndex. Some bugs are fixed.
2.2.8 Feature optimization The memory usage during zstd compression is optimized.
2.2.7 New features A feature that allows you to export ApsaraDB for Lindorm (Lindorm) data in sequence is added. The feature must be used together with Lindorm Tunnel Service (LTS).
2.2.5 New features A feature that allows you to export incremental data of Lindorm is added. The feature must be used together with LTS.
2.2.1 Feature optimization The SearchIndex feature is optimized and some bugs are fixed.
2.1.30 Feature optimization The algorithm for selecting flush regions when write hotspots occur is optimized.
2.1.26 Feature optimization The memory overhead of BucketCache is optimized for instances with lower specifications.
2.1.25 Feature optimization The amount of redundant data that is retrieved for reverse scans is reduced.
2.1.23 Feature optimization The memory management for small-memory servers is optimized.
2.1.21 Feature optimization We recommend that you upgrade your cluster to this version or a later version.
  • The write throughput is optimized.
  • The performance of reverse scans is optimized.
  • The speed at which hot data is archived to cold storage is optimized.
2.1.17 Feature optimization The SearchIndex feature is optimized.
2.1.15 Feature optimization The SearchIndex feature is optimized and some bugs are fixed.
2.1.12 Feature optimization The SearchIndex feature is optimized and the issues that occur during bulk loading are fixed.
2.1.10 New features The SearchIndex feature is supported.
Feature optimization The hot and cold data separation feature is optimized.
2.1.9 New features The SearchIndex feature is supported and some bugs are fixed.
2.1.8 New features The Cold storage and Cold and hot data separation features are supported.