- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Float this Question for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
What is active and passive NameNode in Hadoop?
- Labels:
-
Apache Hadoop
Created ‎02-07-2018 12:05 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
What is the need of passive NameNode in Hadoop?
Created ‎02-07-2018 07:12 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
There is no such thing as a "passive" NameNode. Are you asking about the HA or non-HA configuration?
- In an HA configuration, there is
- Active NameNode that serves user requests.
- Standby NameNode that generates periodic checkpoints. It can also take over the role of the Active if the previously active NameNode dies or becomes unresponsive.
- In a non-HA configuration
- Primary NameNode that serves user requests.
- Secondary NameNode that generates periodic checkpoints. A secondary NameNode can never become the primary.
The terminology is unfortunately confusing.
Created ‎02-07-2018 06:36 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The passive NameNode can be used in high availability configurations, to prevent single point of failure: https://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.6.4/bk_hadoop-high-availability/content/ch_HA-N....
Created ‎02-07-2018 06:45 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Also check out info on the standby NameNode: https://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.6.4/bk_hdfs-administration/content/get_ready_to...
Created ‎02-07-2018 07:12 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
There is no such thing as a "passive" NameNode. Are you asking about the HA or non-HA configuration?
- In an HA configuration, there is
- Active NameNode that serves user requests.
- Standby NameNode that generates periodic checkpoints. It can also take over the role of the Active if the previously active NameNode dies or becomes unresponsive.
- In a non-HA configuration
- Primary NameNode that serves user requests.
- Secondary NameNode that generates periodic checkpoints. A secondary NameNode can never become the primary.
The terminology is unfortunately confusing.
