Dear Wiki user, You have subscribed to a wiki page or wiki category on "Hadoop Wiki" for change notification.
The following page has been changed by KonstantinShvachko: http://wiki.apache.org/hadoop/NameNode ------------------------------------------------------------------------------ - The NameNode is the centerpiece of an HDFS filesystem. It keeps the directory tree of all files in the filesystem, and tracks where across the cluster the files are kept. It does not store any of these files itself. + The NameNode is the centerpiece of an HDFS file system. It keeps the directory tree of all files in the file system, and tracks where across the cluster the file data is kept. It does not store the data of these files itself. Client applications talk to the NameNode whenever they wish to locate a file, or when they want to add/copy/move/delete a file. The NameNode responds the successful requests by returning a list of relevant DataNode servers where the data lives. - The NameNode is a Single Point of Failure for the HDFS Cluster. HDFS is not currently a HighAvailability filesystem. When the NameNode goes down, the filesystem goes offline. There is an optional SecondaryNameNode that can be hosted on a separate machine. It only merges the edits file into the fsimage file and does not provide any real redundancy. + The NameNode is a Single Point of Failure for the HDFS Cluster. HDFS is not currently a High Availability system. When the NameNode goes down, the file system goes offline. There is an optional SecondaryNameNode that can be hosted on a separate machine. It only creates checkpoints of the namespace by merging the edits file into the fsimage file and does not provide any real redundancy. It is essential to look after the NameNode. Here are some recommendations from production use * Use a good server with lots (15GB+) of RAM. - * Consider using fast RAID5 storage for keeping the index. - * List more than one name node directory in the configuration, so that multiple copies of the indices will be stored. As long as the directories are on separate disks, a single full disk will not corrupt the index. + * List more than one name node directory in the configuration, so that multiple copies of the file system meta-data will be stored. As long as the directories are on separate disks, a single disk failure will not corrupt the meta-data. - * Configure the name node to store one set of transaction logs on a separate disk from the index. + * Configure the name node to store one set of transaction logs on a separate disk from the image. - * Configure the name node to store another set of transaction logs to a network mounted disk. + * Configure the name node to store another set of transaction logs to a network mounted disk. * Monitor the disk space available to the NameNode. If is getting low, add more storage. * Do not host DataNode, JobTracker or TaskTracker services on the same system.
