Reply
Highlighted
Contributor
Posts: 29
Registered: ‎04-08-2016
Accepted Solution

name node log full of WARN Please update the DataNode to the same version of Hadoop HDFS as the Name

RedHat 6.7

 

Parcel: 5.7.0-1.cdh5.7.0.p0.45

 

RPMs:

cloudera-manager-server-5.7.0-1.cm570.p0.76.el6.x86_64
cloudera-manager-agent-5.7.0-1.cm570.p0.76.el6.x86_64
cloudera-manager-daemons-5.7.0-1.cm570.p0.76.el6.x86_64

 

host monitor is running and the cluster is green, no issues.

 

We are running Parcels, so everything is same version, but see this error over and over in the name log:

 

2016-08-24 16:06:51,497 WARN BlockStateChange: BLOCK* processReport: Report from the DataNode (dc43ee8e-42ea-4d17-afb0-dc4816c5e4ca) is unsorted. This will cause overhead on the NameNode which needs to sort the Full BR. Please update the DataNode to the same version of Hadoop HDFS as the NameNode (2.6.0-cdh5.7.0).

 

Cloudera Employee
Posts: 92
Registered: ‎08-01-2013

Re: name node log full of WARN Please update the DataNode to the same version of Hadoop HDFS as the

Hi,

That WARN message was introduced by an improvement per HDFS-9260. However, as our backport missed sorting, the WARN appears.

It already gets addressed in: https://github.com/cloudera/hadoop-common/commit/95c7d8fbe122de617d11b6e4ea7d101803d0bd12 and the fix is available in CDH releases of 5.7.2 onwards and also in the 5.8.x series.
Posts: 1,903
Kudos: 436
Solutions: 307
Registered: ‎07-31-2013

Re: name node log full of WARN Please update the DataNode to the same version of Hadoop HDFS as the

Adding onto @dice's post, this WARN does not impair any current functionality your HDFS is performing. It can be ignored until you are able to grab the bug-fix via the update to 5.7.2 or higher.

See also the past community topic on the same question: http://community.cloudera.com/t5/Storage-Random-Access-HDFS/quot-Report-from-the-DataNode-datanodeUu...