question Re: could only be replicated to 0 nodes instead of minReplication (=1). There are 2 datanode(s) running and no node(s) are excluded in this operation in Support Questions

could only be replicated to 0 nodes instead of minReplication (=1). There are 2 datanode(s) running and no node(s) are excluded in this operation

hanumanth — Tue, 30 May 2023 04:32:24 GMT

Hi Team,

Job failing due to below error, can any one help me on this.

could only be replicated to 0 nodes instead of minReplication (=1).  There are 2 datanode(s) running and no node(s) are excluded in this operation

Re: could only be replicated to 0 nodes instead of minReplication (=1). There are 2 datanode(s) running and no node(s) are excluded in this operation

hanumanth — Tue, 30 May 2023 07:07:30 GMT

Hi Team,

Any suggestions??

Re: could only be replicated to 0 nodes instead of minReplication (=1). There are 2 datanode(s) running and no node(s) are excluded in this operation

rki_ — Mon, 05 Jun 2023 07:21:33 GMT

Hi @hanumanth There could be various factors that could cause such issues.

Can you check what the Namenode was logging at the same time?

It could be some Block Placement issue as the Datanodes are considered for the operation but something has restricted the write/read.

Re: could only be replicated to 0 nodes instead of minReplication (=1). There are 2 datanode(s) running and no node(s) are excluded in this operation

DianaTorres — Fri, 09 Jun 2023 00:17:21 GMT

@hanumanth Has the reply helped resolve your issue? If so, please mark the appropriate reply as the solution, as it will make it easier for others to find the answer in the future.Thanks.

Re: could only be replicated to 0 nodes instead of minReplication (=1). There are 2 datanode(s) running and no node(s) are excluded in this operation

hanumanth — Thu, 13 Jul 2023 12:23:55 GMT

Hi all,

Issue has been resolved , while running job at staging level it requires more space in HDFS but no sufficient space in HDFS after added more disks , then job got success.