My Oracle Support Banner

On BDA V4.2/CDH 5.4.0 "datanode.BPServiceActorActionException: Failed to report bad block" Reported Over and Over for Some DataNodes (Doc ID 2129365.1)

Last updated on JANUARY 06, 2020

Applies to:

Big Data Appliance Integrated Software - Version 4.2.0 and later
Linux x86-64

Symptoms

NOTE: In the examples that follow, user details, cluster names, hostnames, directory paths, filenames, etc. represent a fictitious sample (and are used to provide an illustrative example only). Any similarity to actual persons, or entities, living or dead, is purely coincidental and not intended in any manner.

On BDA V4.2/CDH 5.4.0 "datanode.BPServiceActorActionException: Failed to report bad block" looks to be in an infinite loop.

In the DataNode logs see output like below repeated over and over:

org.apache.hadoop.hdfs.server.datanode.BPServiceActorActionException: Failed to report bad block
BP-1375062222-<PRIVATE_IP_HOST>-1399628088708:blk_1149529116_75876399 to namenode:
2016-03-25 00:20:04,944 WARN org.apache.hadoop.hdfs.server.datanode.DataNode: Failed to report bad block
BP-1375062222-<PRIVATE_IP_HOST>-1399628088708:blk_1149529116_75876399 to namenode: host.example.com/<PRIVATE_IP_HOST>:8022

Searching for "Failed to report bad block" in the DataNode log file shows a very large number of entries.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.