Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via flink-user by Stefan Bunk, 1 year ago
Bad response ERROR for block BP-1944967336-172.16.21.111-1412785070309:blk_1075716642_1975988 from datanode 172.16.19.81:50010
via spark-user by maxdml, 1 year ago
Bad response ERROR for block BP-845049430-155.99.144.31-1435598542277:blk_1073742427_1758 from datanode x.x.x.x:50010
via csdn.net by Unknown author, 2 years ago
Bad response ERROR for block BP-1386326728-10.39.2.131-1382089338395:blk_1394153869_320473223 from datanode 10.39.1.90:50010
via serverfault.com by Unknown author, 2 years ago
Bad response ERROR for block BP-845049430-155.99.144.31-1435598542277:blk_1073742427_1758 from datanode x.x.x.x:50010
via Google Groups by Tao Xiao, 2 years ago
Bad response ERROR for block BP-898918553-10.134.101.112-1393904898674:blk_1078908600_5176868 from datanode 10.134.101.110:50010
via Server Fault by Bacon
, 1 year ago
Bad response ERROR for block BP-845049430-155.99.144.31-1435598542277:blk_1073742427_1758 from datanode x.x.x.x:50010
java.io.IOException: Bad response ERROR for blockBP-1944967336-172.16.21.111-1412785070309:blk_1075716642_1975988 fromdatanode 172.16.19.81:50010 at org.apache.hadoop.hdfs.DFSOutputStream$DataStreamer$ResponseProcessor.run(DFSOutputStream.java:732)