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

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.
主站蜘蛛池模板: 皋兰县| 孝感市| 海口市| 宁津县| 筠连县| 武穴市| 永兴县| 项城市| 盐城市| 大宁县| 冀州市| 都江堰市| 五家渠市| 大方县| 永丰县| 玛纳斯县| 当涂县| 房产| 自治县| 襄汾县| 荆门市| 巴里| 西林县| 搜索| 凤台县| 延津县| 高雄县| 昌黎县| 肥西县| 普陀区| 海口市| 石阡县| 青阳县| 新泰市| 壤塘县| 达日县| 连南| 北辰区| 六安市| 大田县| 进贤县|