hadoop上传文件错误File /home/input/file1.txt._COPYING_ could only be replicated to 0 nodes instead of minR

ゝ一纸荒年。 2022-05-26 12:37 236阅读 0赞

搭建好hadoop后使用hadoop dfs -put 命令上传文件发现失败,报了以下错误:

  1. [java] view plain copy
  2. 14/08/18 15:18:03 WARN hdfs.DFSClient: DataStreamer Exception
  3. org.apache.hadoop.ipc.RemoteException(java.io.IOException): File /home/input/file1.txt._COPYING_ 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.
  4. at org.apache.hadoop.hdfs.server.blockmanagement.BlockManager.chooseTarget(BlockManager.java:1384)
  5. at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getAdditionalBlock(FSNamesystem.java:2477)
  6. at org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.addBlock(NameNodeRpcServer.java:555)
  7. at org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolServerSideTranslatorPB.addBlock(ClientNamenodeProtocolServerSideTranslatorPB.java:387)
  8. at org.apache.hadoop.hdfs.protocol.proto.ClientNamenodeProtocolProtos$ClientNamenodeProtocol$2.callBlockingMethod(ClientNamenodeProtocolProtos.java:59582)
  9. at org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:585)
  10. at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:928)
  11. at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2048)
  12. at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2044)
  13. at java.security.AccessController.doPrivileged(Native Method)
  14. at javax.security.auth.Subject.doAs(Subject.java:396)
  15. at org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1491)
  16. at org.apache.hadoop.ipc.Server$Handler.run(Server.java:2042)
  17. at org.apache.hadoop.ipc.Client.call(Client.java:1347)
  18. at org.apache.hadoop.ipc.Client.call(Client.java:1300)
  19. at org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:206)
  20. at $Proxy9.addBlock(Unknown Source)
  21. at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  22. at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
  23. at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  24. at java.lang.reflect.Method.invoke(Method.java:597)
  25. at org.apache.hadoop.io.retry.RetryInvocationHandler.invokeMethod(RetryInvocationHandler.java:186)
  26. at org.apache.hadoop.io.retry.RetryInvocationHandler.invoke(RetryInvocationHandler.java:102)
  27. at $Proxy9.addBlock(Unknown Source)
  28. at org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolTranslatorPB.addBlock(ClientNamenodeProtocolTranslatorPB.java:330)
  29. at org.apache.hadoop.hdfs.DFSOutputStream$DataStreamer.locateFollowingBlock(DFSOutputStream.java:1226)
  30. at org.apache.hadoop.hdfs.DFSOutputStream$DataStreamer.nextBlockOutputStream(DFSOutputStream.java:1078)

看它的报错信息好像是节点没有启动,但是我的节点都启动起来了,使用jps也能查看到节点信息。
使用hadoop dfsadmin -report命令查看磁盘使用情况,发现出现以下问题:

  1. [java] view plain copy
  2. Configured Capacity: 0 (0 B)
  3. Present Capacity: 0 (0 B)
  4. DFS Remaining: 0 (0 B)
  5. DFS Used: 0 (0 B)
  6. DFS Used%: NaN%
  7. Under replicated blocks: 0
  8. Blocks with corrupt replicas: 0
  9. Missing blocks: 0
  10. -------------------------------------------------
  11. Datanodes available: 0 (0 total, 0 dead)

节点下存储空间都是空的,问题应该就是出现在这了。
查阅资料发现造成这个问题的原因可能是使用hadoop namenode -format格式化时格式化了多次造成那么spaceID不一致,解决方案:

1、停止集群(切换到/sbin目录下)
$./stop-all.sh

2、删除在hdfs中配置的data目录(即在core-site.xml中配置的hadoop.tmp.dir对应文件件)下面的所有数据;
$ rm -rf /home/hadoop/hdpdata/*

3、重新格式化namenode(切换到hadoop目录下的bin目录下)
$ ./hadoop namenode -format

4、重新启动hadoop集群(切换到hadoop目录下的sbin目录下)
$./start-all.sh

在使用hadoop dfsadmin -report查看使用情况,结果如下图所示:

ok没有错误了。再次上传文件,成功。

转载:http://blog.csdn.net/weiyongle1996/article/details/74094989

发表评论

表情:
评论列表 (有 0 条评论,236人围观)

还没有评论,来说两句吧...

相关阅读