All Products
Search
Document Center

E-MapReduce:EMR HBase versions

Last Updated:Feb 19, 2024

This topic describes the compatibility, selection suggestions, and release notes for E-MapReduce (EMR) HBase versions.

Release notes for EMR HBase

EMR HBase is released together with EMR. The major versions of EMR include EMR V3.X and EMR V5.X. EMR V3.X corresponds to Hadoop 2.X and HBase 1.X. EMR V5.X corresponds to Hadoop 3.X and HBase 2.X.

The following tables describe the EMR versions, the mappings between EMR versions and the versions of Hadoop, HBase, and Phoenix, and the features that are supported by HBase of different versions.

EMR V5.X series

EMR version

Hadoop version

HBase version

Phoenix version

New feature

EMR 5.8.0

3.2.1

2.3.4

5.1.2

The compute-storage separation architecture is supported.

EMR 5.9.0

3.2.1

2.4.9

5.1.2

  • The high security mode is supported.

  • CompactedConcurrentSkipListMap (CCSMap) is supported. In this case, the write performance is more than 30% higher than the write performance of open source HBase.

EMR 5.10.0

3.2.1

2.4.9

5.1.2

  • Ranger is integrated with HBase.

  • Knox is integrated with HBase.

  • Cold data in HBase tables can be analyzed.

EMR 5.11.0

3.2.1

2.4.9

5.1.2

  • JDK 11 is supported.

  • ThriftServer 2 is supported.

  • The default value of the hbase.block.data.cachecompressed parameter is changed to true.

EMR 5.11.1

3.2.1

2.4.9

5.1.2

N/A

EMR 5.12.0

3.2.1

2.4.9

5.1.2

  • By default, OSS-HDFS is used to store HBase data in the HFile format.

  • OSS-HDFS is used to store write-ahead logging (WAL) logs of HBase.

EMR 5.12.2

3.2.1

2.4.9

5.1.2

EMR 5.13.1

3.2.1

2.4.9

5.1.2

N/A

EMR 5.14.2

3.2.1

2.4.9

5.1.2

N/A

EMR 5.15.1

3.2.1

2.4.9

5.1.2

Configuration items are added on the Configure tab of the HBase service page, and you can select the version of HBase Thrift Server based on your business requirements. The version of HBase Thrift Server can be v1 or v2.

EMR V3.X series

EMR version

Hadoop version

HBase version

Phoenix version

New feature

EMR 3.42.0

2.8.5

1.4.9

4.14.1

The compute-storage separation architecture is supported.

EMR 3.43.0

2.8.5

1.7.1

4.16.1

The high security mode is supported.

EMR 3.43.1

2.8.5

1.7.1

4.16.1

EMR 3.44.0

2.8.5

1.7.1

4.16.1

  • Cold data in HBase tables can be analyzed.

  • Knox is integrated with HBase.

  • Cold data in HBase tables can be analyzed.

EMR 3.44.1

2.8.5

1.7.1

4.16.1

  • Ranger is supported.

  • The following issue is fixed: When you add a service, OSS-HDFS cannot be selected for data storage.

EMR 3.45.0

2.8.5

1.7.1

4.16.1

  • ThriftServer 2 is supported.

  • The default value of the hbase.block.data.cachecompressed parameter is changed to true.

EMR 3.45.1

2.8.5

1.7.1

4.16.1

EMR 3.46.0

2.8.5

1.7.1

4.16.1

  • By default, OSS-HDFS is used to store HBase data in the HFile format.

  • OSS-HDFS is used to store write-ahead logging (WAL) logs of HBase.

EMR 3.46.2

2.8.5

1.7.1

4.16.1

EMR 3.47.1

2.8.5

1.7.1

4.16.1

N/A

EMR 3.48.2

2.8.5

1.7.1

4.16.1

N/A

EMR 3.49.1

2.8.5

1.7.1

4.16.1

Configuration items are added on the Configure tab of the HBase service page, and you can select the version of HBase Thrift Server based on your business requirements. The version of HBase Thrift Server can be v1 or v2.

HBase version compatibility

HBase follows the Semantic Versioning (SemVer) specification. The version numbers of HBase are in the Major.Minor.Patch format, which specifies the compatibility between versions. For HBase 2.4.9, the major version is 2, the minor version is 4, and the patch version is 9.

Compatibility

Major

Minor

Patch

Client-Server API or protocol compatibility

N

Y

Y

Server-Server API or protocol compatibility

N

Y

Y

File format compatibility

N

Y

Y

Client API compatibility

N

Y

Y

Note

In the table, N indicates incompatible, and Y indicates compatible.

For more information about the compatibility of HBase versions, see Apache HBase Reference Guide.

  • If you upgrade HBase across major versions, compatibility cannot be ensured.

  • If you upgrade HBase across minor versions, compatibility can be ensured.

  • If you upgrade HBase across patch versions, compatibility can be ensured.

HBase version selection

  • If you want to migrate data from a self-managed HBase cluster to an EMR HBase cluster, you can select an EMR HBase cluster whose HBase version is close to the HBase version of the self-managed HBase cluster.

  • If you do not have a self-managed cluster, you can select an HBase version that corresponds to EMR V3.X or EMR V5.V based on the version of Hadoop on which your cluster depends.