question name node log full of WARN Please update the DataNode to the same version of Hadoop HDFS as the Name in Archives of Support Questions (Read Only)

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

ScottChris — Wed, 24 Aug 2016 22:27:44 GMT

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).

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

dice — Thu, 25 Aug 2016 03:04:39 GMT

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.

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

Harsh J — Thu, 25 Aug 2016 04:04:47 GMT

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-datanodeUuid-is-unsorted-quot/m-p/41943#M2188