All Products
Search
Document Center

ApsaraDB for HBase:Minor version updates

Last Updated:Mar 28, 2026

Update the minor version of an ApsaraDB for HBase cluster from the console to get the latest features, performance improvements, and stability fixes.

Important

Minor version updates use a rolling restart, so your cluster stays available throughout the process. Before each RegionServer restarts, all its regions are moved to other servers to minimize business impact. Network jitter may occur, but the cluster remains accessible.

  • A cluster with 2 core nodes and 100 regions typically completes in under 10 minutes.

  • A large cluster with thousands of regions may take over an hour.

Update the minor version

  1. Log on to the ApsaraDB for HBase console.

  2. In the upper-left corner of the top navigation bar, select the region of your instance.

  3. On the Clusters page, click the ID of the target instance.

  4. In the left navigation pane, click Database Connection.

  5. In the upper-right corner of the page, click Upgrade Minor Version.

Release notes

VersionRelease dateCategoryDescription
2.8.6January 21, 2026New features
  • Set SQL query memory limits using the QUERY_MAX_MEM system parameter.
  • Use the INSERT INTO SELECT syntax.
  • Batch updates and deletes are enabled by default for better performance.
  • Multiple JSON functions are now supported.
  • Use SQL to show or kill queries initiated by HBase clients.
Optimizations
  • Improved HBase compatible layer performance.
  • Improved SQL read and write performance for tables with many columns.
  • Improved write performance for Multi-zone Deployment (Basic).
  • Optimized the index building process.
  • Other stability improvements.
2.8.2September 7, 2025New featuresUse Lindorm SQL to estimate the row count of statistical tables.
Optimizations
  • Improved user experience for range deletion, column deletion, and index building.
  • Improved load balancing for instances with many tables.
  • Improved SQL on HBase compatibility and performance.
  • Improved HBase protocol compatibility.
  • Other stability fixes.
2.8.0March 27, 2025New features
Optimizations
  • Added memory protection for SQL queries to prevent out of memory (OOM) errors.
  • Fixed performance degradation when the SQL engine rolls back to sqlv2.
  • Improved pushdown performance for global queries (Select *).
  • Fixed SQL performance degradation after Secure Sockets Layer (SSL) encryption is enabled.
  • Improved HBase protocol and SQL on HBase compatibility.
  • Improved cache replacement speed when query patterns change frequently.
2.7.6December 6, 2024New features
Optimizations
  • Improved aggregation request performance.
  • Fixed occasional failures when building secondary indexes on historical data.
  • Improved request retry logic to reduce errors during shard migration or splitting.
  • Improved execution logic for IN requests to handle queries with many IN clauses more efficiently.
  • Refined automatic hot spot detection and resolution for finer-grained identification and handling.
  • Improved HBase protocol compatibility and MySQL syntax support.
  • Other stability fixes.
2.7.1July 11, 2024New features
Optimizations
  • Improved SQL point query performance.
  • Build indexes on historical data for multiple index tables of a single table simultaneously.
  • More detailed status and progress information for building secondary indexes on historical data.
  • Other stability fixes and improved MySQL syntax compatibility.
2.6.5March 25, 2024New features
Optimizations
  • Improved MySQL syntax compatibility.
  • Lindorm SQL supports physical plan reuse to improve query performance.
  • Building secondary indexes on historical data is no longer affected by cold storage.
  • Improved native HBase client protocol compatibility. If you use an open source HBase client to access Lindorm, upgrade the LindormTable engine to this version or later.
2.6.2November 8, 2023New featuresMySQL-compatible protocol support. See Use the MySQL protocol (recommended).
2.5.6August 18, 2023Optimizations
  • Fixed HBase protocol compatibility issues.
  • Fixed unbalanced loads across multiple groups.
  • Other stability fixes.
2.5.3May 24, 2023New featuresWildcard columns are now supported.
Optimizations
  • Fixed SQL request timeouts during short-circuit reads and writes.
    Note

    For a better read and write experience, upgrade the LindormTable engine to 2.5.3 or later if you use SQL.

  • Fixed a compatibility issue with the batch interface of open source HBase clients.
  • Fixed excessive meta requests when using open source HBase clients.
2.5.2April 19, 2023New features

Lindorm SQL supports deleting existing columns from a table. For more information, see ALTER TABLE.

Optimizations
  • Improved experience for using SQL to access ApsaraDB for HBase tables.
  • Improved query experience in hot and cold data separation scenarios.
  • Improved asynchronous audit logging performance.
  • Improved HBase client protocol compatibility.
  • Increased the file monitoring limit per region.
  • Improved Aggregate statement execution efficiency.
  • Reduced CPU consumption from data expiration in short TTL scenarios.
2.4.3March 10, 2023Optimizations
  • Improved Lindorm SQL user experience.
  • Other stability fixes.
2.4.2December 13, 2022New features
Optimizations
  • Improved JSON data type user experience.
  • Other stability fixes.
2.4.1November 1, 2022Optimizations
  • Improved Lindorm Ganos spatiotemporal feature user experience.
  • Fixed bugs in Lindorm SQL.
2.4.0October 9, 2022New features

You can use SQL to access HBase tables.

OptimizationsImproved Lindorm SQL user experience.
2.3.4August 30, 2022OptimizationsImproved Lindorm SQL user experience.
2.3.3August 16, 2022Optimizations
  • Added automatic hot spot detection and handling.
  • Added ST_DWithin and ST_DWithinSphere functions to the spatiotemporal engine.
  • Other stability fixes.
2.3.2August 2, 2022Optimizations
2.3.1June 30, 2022New featuresLindorm Ganos spatiotemporal features.
2.2.21April 25, 2022Optimizations
  • Reduced DirectMemory consumption during writes.
  • Improved load balancing policy.
  • Improved compaction parameters with automatic adjustment support.
  • Improved index building speed.
  • Improved SQL read and write performance.
2.2.20March 16, 2022Optimizations
  • Improved write performance for large key-value pairs.
  • Lindorm SQL supports reading multiple data versions and writing data with custom timestamps.
  • Other performance fixes.
2.2.19February 9, 2022New featuresLindorm SQL supports dynamic columns and SQL layer monitoring.
Optimizations
  • Fixed delayed metadata updates after Lindorm SQL table properties are modified.
  • Other stability fixes.
2.2.18January 5, 2022Optimizations
  • Improved Lindorm SQL performance.
  • Fixed time zone issues for Date and Time data types in Lindorm SQL.
  • Other stability fixes.
2.2.17December 17, 2021Optimizations
  • Fixed bugs in Lindorm SQL.
  • Improved the online speed of cold storage regions. If you use cold storage, upgrade the LindormTable engine to 2.2.17 or later.
2.2.16November 12, 2021Optimizations
  • Improved Lindorm SQL syntax. If you use Lindorm SQL, upgrade LindormTable to 2.2.16 or later.
  • Improved disk flush logic to prevent out of memory errors when there are too many regions.
  • Other bug fixes.
2.2.15October 18, 2021OptimizationsImproved Lindorm SQL usability and fixed issues where tables failed to be created in some cases and access to strongly consistent tables failed. Upgrade to this version or later.
2.2.12September 6, 2021Optimizations
  • Improved compaction policy efficiency.
  • Optimized the amount of data returned by Scan operations.
2.2.11August 25, 2021New features
  • Lindorm SQL statement support.
  • High-performance native secondary indexes.
2.2.10August 12, 2021OptimizationsFixed failures for cold storage requests caused by network jitter. Upgrade to this version or later.
2.2.9June 9, 2021New featuresThe multi-dimensional index (SearchIndex) feature supports dynamic tokenizer configuration generation, with bug fixes.
2.2.8March 25, 2021OptimizationsOptimized memory usage during zstd compression.
2.2.7March 11, 2021New featuresSequential data export from Lindorm. Requires Lindorm Tunnel Service (LTS).
2.2.5January 7, 2021New featuresIncremental data export from Lindorm. Requires LTS.
2.2.1September 9, 2020OptimizationsImproved multi-dimensional index (SearchIndex) feature with bug fixes.
2.1.30October 26, 2020OptimizationsImproved region selection algorithm for flushing in write hot spot scenarios.
2.1.26October 9, 2020OptimizationsReduced BucketCache memory overhead for small-specification instances.
2.1.25September 30, 2020OptimizationsReduced redundant data retrieved during reverse scans.
2.1.23September 22, 2020OptimizationsImproved memory management for low-memory machine types.
2.1.21July 20, 2020OptimizationsUpgrade to this version or later.
  • Improved write throughput.
  • Improved reverse scan performance.
  • Improved archiving speed from hot storage to cold storage in hot and cold data separation scenarios.
2.1.17March 20, 2020OptimizationsImproved usability of the multi-dimensional index (SearchIndex) feature.
2.1.15February 6, 2020OptimizationsImproved multi-dimensional index (SearchIndex) feature with bug fixes.
2.1.12December 16, 2019OptimizationsImproved multi-dimensional index (SearchIndex) feature and fixed issues during bulk load.
2.1.10November 16, 2019New featuresMulti-dimensional index (SearchIndex) feature.
OptimizationsImproved hot and cold data separation feature.
2.1.9October 8, 2019New featuresSearchIndex feature with bug fixes.
2.1.8September 9, 2019New featuresCold storage and hot and cold data separation features.