You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-commits@hadoop.apache.org by Apache Wiki <wi...@apache.org> on 2012/02/22 16:38:34 UTC

[Hadoop Wiki] Update of "CouldOnlyBeReplicatedTo" by SteveLoughran

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Hadoop Wiki" for change notification.

The "CouldOnlyBeReplicatedTo" page has been changed by SteveLoughran:
http://wiki.apache.org/hadoop/CouldOnlyBeReplicatedTo?action=diff&rev1=3&rev2=4

Comment:
HDFS-2964

   * No DataNode instances being up and running. Action: look at the servers, see if the processes are running.
   * The DataNode instances cannot talk to the server, through networking or Hadoop configuration problems. Action: look at the logs of one of the [[DataNode|DataNodes]].
   * Your DataNode instances have no hard disk space in their configured data directories. Action: look at the dfs.data.dir list in the node configurations, verify that at least one of the directories exists, and is writeable by the user running the Hadoop processes. Then look at the logs.
-  * Your DataNode instances have run out of space. Look at the disk capacity via the Namenode web pages. Delete old files. Compress under-used files. Buy more disks for existing servers (if there is room), upgrade the existing servers to bigger drives, or add some more servers.  Note that your datanode takes the freespace there is and subtracts "dfs.datanode.du.reserved" so even if there is free space, some times the datanode believes there isn't.
+  * Your DataNode instances have run out of space. Look at the disk capacity via the Namenode web pages. Delete old files. Compress under-used files. Buy more disks for existing servers (if there is room), upgrade the existing servers to bigger drives, or add some more servers.  
+  * The reserved space for a DN (as set in dfs.datanode.du.reserved is greater than the remaining free space, so the DN thinks it has no free space
   * You may also get this message due to permissions, eg if JT can not create jobtracker.info on startup.
  
  This is not a problem in Hadoop, it is a problem in your cluster that you are going to have to fix on your own. Sorry.