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

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.
主站蜘蛛池模板: 沧源| 北流市| 朝阳市| 南平市| 辽阳市| 陆良县| 甘南县| 南开区| 遵化市| 彰武县| 托克托县| 伊宁县| 舞钢市| 喀什市| 芮城县| 德安县| 松潘县| 革吉县| 依安县| 白山市| 滕州市| 虹口区| 广平县| 桑植县| 福鼎市| 鹿邑县| 临邑县| 宁化县| 城市| 聂拉木县| 得荣县| 松溪县| 平安县| 嘉黎县| 汾阳市| 新宁县| 大港区| 临武县| 小金县| 高安市| 米林县|