This topic describes how to update the minor version of an ApsaraDB for HBase cluster in the ApsaraDB for HBase console. This topic also describes the feature updates in each minor version.
The update does not interrupt the ApsaraDB for HBase service. The system performs a rolling update on the ApsaraDB for HBase cluster. Before the RegionServer restarts, data of all regions is moved to other servers to minimize the impact on your workloads. Jitters may occur during the update, but the ApsaraDB for HBase cluster remains available. You can perform minor version updates based on your business requirements.
The amount of time that is required to update the minor version of an ApsaraDB for HBase cluster varies based on the size of the ApsaraDB for HBase cluster and the number of regions in the ApsaraDB for HBase cluster. A larger cluster requires more time to update the minor version. In most cases, ApsaraDB for HBase takes less than 10 minutes to update a cluster that contains two core nodes and 100 regions. ApsaraDB for HBase may take more than 1 hour to update a cluster that contains a large number of core nodes and more than 1,000 regions.
Procedure
Log on to the ApsaraDB for HBase console.
In the top navigation bar, select the region where the cluster that you want to manage is deployed.
On the Clusters page, click the ID of the cluster that you want to manage.
In the left-side navigation pane, click Database Connection.
In the upper-right corner, click Upgrade Minor Version.
Version description
Version number | Release date | Category | Description |
2.5.3 | May 24, 2023 | New feature | Columns can be queried by using wildcards. |
Feature optimization |
| ||
2.5.2 | April 19, 2023 | New feature | ApsaraDB for HBase allows you to delete columns from a table by using Lindorm SQL statements. For more information, see ALTER TABLE. |
Feature optimization |
| ||
2.4.3 | March 10, 2023 | Feature optimization |
|
2.4.2 | December 13, 2022 | New features |
|
Feature optimization |
| ||
2.4.1 | November 01, 2022 | Feature optimization |
|
2.4.0 | October 09, 2022 | New feature | Access to an HBase table by using SQL statements is supported. For more information, see Use SQL statements to access an HBase table. |
Feature optimization | The user experience of using Lindorm SQL statements is optimized. | ||
2.3.4 | August 30, 2022 | Feature optimization | The user experience of using Lindorm SQL statements is optimized. |
2.3.3 | August 16, 2022 | Feature optimization |
|
2.3.2 | August 02, 2022 | Feature optimization |
|
2.3.1 | June 30, 2022 | New feature | Lindorm Ganos is supported. For more information, see Overview. |
2.2.21 | April 25, 2022 | Feature optimization |
|
2.2.20 | March 16, 2022 | Feature optimization |
|
2.2.19 | February 09, 2022 | New feature | Dynamic columns and SQL monitoring are supported in Lindorm SQL. |
Feature optimization |
| ||
2.2.18 | January 05, 2022 | Feature optimization |
|
2.2.17 | December 17, 2021 | Feature optimization |
|
2.2.16 | November 12, 2021 | Feature optimization |
|
2.2.15 | October 18, 2021 | Feature optimization | The performance of using Lindorm SQL statements is optimized to fix the following bugs: Tables fail to be created, and data that requires strong consistency fails to be read from tables. We recommend that you update the version of your cluster to 2.2.15 or later. |
2.2.12 | September 06, 2021 | Feature optimization |
|
2.2.11 | August 25, 2021 | New features |
|
2.2.10 | August 12, 2021 | Feature optimization | The following issue is fixed: Errors occur due to network jitters when cold data is requested. We recommend that you update the version of your cluster to 2.2.10 or later. |
2.2.9 | June 09, 2021 | New feature | A feature that allows you to dynamically generate tokenizer configurations is added to SearchIndex, and some bugs are fixed. |
2.2.8 | March 25, 2021 | Feature optimization | The memory usage issue that occurs when data is being compressed by using zstd is fixed. |
2.2.7 | March 11, 2021 | New feature | A feature that allows you to export data from Lindorm in sequence is added. This feature must be used together with Lindorm Tunnel Service (LTS). |
2.2.5 | January 07, 2021 | New feature | A feature that allows you to export incremental data from Lindorm is added. This feature must be used together with LTS. |
2.2.1 | September 09, 2020 | Feature optimization | The SearchIndex feature is optimized, and some bugs are fixed. |
2.1.30 | October 26, 2020 | Feature optimization | The algorithm for selecting flush regions when write hotspots occur is optimized. |
2.1.26 | October 09, 2020 | Feature optimization | The memory overhead of BucketCache is reduced for clusters with low specifications. |
2.1.25 | September 30, 2020 | Feature optimization | The volume of redundant data that is retrieved for reverse scans is reduced. |
2.1.23 | September 22, 2020 | Feature optimization | Memory management is optimized for servers with small memory. |
2.1.21 | July 20, 2020 | Feature optimization | We recommend that you update the version of your cluster to 2.1.21 or later.
|
2.1.17 | March 20, 2020 | Feature optimization | The SearchIndex feature is optimized. |
2.1.15 | February 06, 2020 | Feature optimization | The SearchIndex feature is optimized, and some bugs are fixed. |
2.1.12 | December 16, 2019 | Feature optimization | The SearchIndex feature is optimized, and the issues that occur during bulk loading are fixed. |
2.1.10 | November 16, 2019 | New feature | The SearchIndex feature is supported. |
Feature optimization | The hot and cold data separation feature is optimized. | ||
2.1.9 | October 08, 2019 | New feature | The SearchIndex feature is supported, and some bugs are fixed. |
2.1.8 | September 09, 2019 | New feature | The cold storage feature and the hot and cold data separation feature are supported. For more information, see Cold storage and Cold and hot data separation. |