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 Google Groups by Steve Chadsey, 1 year ago
via Google Groups by Christian Heindl, 2 years ago
via Google Groups by, 2 years ago
via Google Groups by justin, 2 years ago
via Atlassian JIRA by Chuck Burt, 1 year ago Failed to replace a bad datanode on the existing pipeline due to no more good datanodes being available to try. (Nodes: current=[DatanodeInfoWithStorage[,DS-a67e1753-7160-4c87-8a87-330732f6ac30,DISK], DatanodeInfoWithStorage[,DS-f42cdbb3-7981-4630-8b98-0ac04bdf92a2,DISK]], original=[DatanodeInfoWithStorage[,DS-a67e1753-7160-4c87-8a87-330732f6ac30,DISK], DatanodeInfoWithStorage[,DS-f42cdbb3-7981-4630-8b98-0ac04bdf92a2,DISK]]). The current failed datanode replacement policy is DEFAULT, and a client may configure this via 'dfs.client.block.write.replace-datanode-on-failure.policy' in its configuration.	at org.apache.hadoop.hdfs.DFSOutputStream$DataStreamer.findNewDatanode(	at org.apache.hadoop.hdfs.DFSOutputStream$DataStreamer.addDatanode2ExistingPipeline(	at org.apache.hadoop.hdfs.DFSOutputStream$DataStreamer.setupPipelineForAppendOrRecovery(	at org.apache.hadoop.hdfs.DFSOutputStream$DataStreamer.processDatanodeError(	at org.apache.hadoop.hdfs.DFSOutputStream$