官术网_书友最值得收藏!

NameNode

NameNode is the gatekeeper for all HDFS-related queries. It serves as a single point for all types of coordination on HDFS data, which is distributed across multiple nodes. NameNode works as a registry to maintain data blocks that are spread across Data Nodes in the cluster. Similarly, the secondary NameNodes keep a backup of active Name Node data periodically (typically every four hours). In addition to maintaining the data blocks, NameNode also maintains the health of each DataNode through the heartbeat mechanism. In any given Hadoop cluster, there can only be one active name node at a time. When an active NameNode goes down, the secondary NameNode takes up responsibility. A filesystem in HDFS is inspired from Unix-like filesystem data structures. Any request to create, edit, or delete HDFS files first gets recorded in journal nodes; journal nodes are responsible for coordinating with data nodes for propagating changes. Once the writing is complete, changes are flushed and a response is sent back to calling APIs. In case the flushing of changes in the journal files fails, the NameNode moves on to another node to record changes.

NameNode used to be single point of failure in Hadoop 1.X; however, in Hadoop 2.X, the secondary name node was introduced to handle the failure condition. In Hadoop 3.X, more than one secondary name node is supported. The same has been depicted in the overall architecture diagram.
主站蜘蛛池模板: 永泰县| 巧家县| 漳浦县| 新巴尔虎右旗| 根河市| 汶上县| 德江县| 鄂托克前旗| 平南县| 古交市| 明溪县| 宁乡县| 喜德县| 墨竹工卡县| 吉林省| 嘉兴市| 芜湖县| 呼伦贝尔市| 离岛区| 平乐县| 阳信县| 衢州市| 宁晋县| 丘北县| 信阳市| 玉山县| 手游| 柏乡县| 渝北区| 井陉县| 新丰县| 延长县| 克东县| 隆昌县| 晋中市| 松阳县| 潮州市| 琼结县| 历史| 资源县| 独山县|