Open In App

Difference Between Hadoop 2.x vs Hadoop 3.x

Last Updated : 24 Jun, 2025
Summarize
Comments
Improve
Suggest changes
Share
Like Article
Like
Report

The Journey of Hadoop Started in 2005 by Doug Cutting and Mike Cafarella. Which is an open-source software build for dealing with the large size Data? The objective of this article is to make you familiar with the differences between the Hadoop 2.x vs Hadoop 3.x version. Obviously, Hadoop 3.x has some more advanced and compatible features than the older versions of Hadoop 2.x.

Hadoop 2.X vs 3.X

Hadoop 2.x vs Hadoop 3.x

FeatureHadoop 2.xHadoop 3.x
LicenseApache 2.0 is used for licensing which is open-source.Apache 2.0 is used for licensing which is open-source.
Minimum supported Java versionJAVA 7 is the minimum compatible version.JAVA 8 is the minimum compatible version.
Fault ToleranceReplication is the only way to handle fault tolerance which is not space optimized.Erasure coding is used for handling fault tolerance.
Data BalancingHDFS balancer is used for Data Balancing.Intra-data node balancer is used which is called via HDFS disk-balancer command-line interface.
Storage Scheme3x Replication Scheme is used.uses eraser encoding in HDFS.
Storage Overhead200% of HDFS is consumed in Hadoop 2.x50% used in Hadoop 3.x means we have more space to work.
YARN Timeline ServiceUses timeline service with scalability issue.Improve the time line service along with improving scalability and reliability of this service.
ScalabilityLimited Scalability, can have upto 10000 nodes in a cluster.Scalability is improved, can have more then 10000 nodes in a cluster.
Default Port Range (32768-61000)Linux ephemeral port range is used as default, which is failed to bind at startup time.Ports used are out of this ephemeral port range.
Compatible File System.HDFS(default), FTP, Amazon S3 and Windows Azure Storage Blobs (WASB) file system.All file systems including Microsoft Azure Data Lake filesystem.
Name Node recoveryManual intervention is needed for the namenode recovery.No need of Manual intervention for name node recovery.

Native Support for Docker / Containers

Not available

Supports Docker-based container execution in YARN, allowing better isolation and dependency management

GPU Support in YARN

Does not support

Supports GPU-aware scheduling in YARN which important for AI/ML workloads

Backward Compatibility

Not all tools supported out-of-box

Backward compatible and supports newer versions of Hive, HBase, etc.

Shell Script Rewrite

Legacy shell scripts

Rewritten shell scripts in better cross-platform compatibility


Article Tags :

Similar Reads