Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

What is active and passive NameNode in Hadoop?

Solved Go to solution
Highlighted

What is active and passive NameNode in Hadoop?

New Contributor

What is the need of passive NameNode in Hadoop?

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted

Re: What is active and passive NameNode in Hadoop?

There is no such thing as a "passive" NameNode. Are you asking about the HA or non-HA configuration?

  1. In an HA configuration, there is
    1. Active NameNode that serves user requests.
    2. 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.
  2. In a non-HA configuration
    1. Primary NameNode that serves user requests.
    2. Secondary NameNode that generates periodic checkpoints. A secondary NameNode can never become the primary.

The terminology is unfortunately confusing.

View solution in original post

3 REPLIES 3

Re: What is active and passive NameNode in Hadoop?

Rising Star

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....

Highlighted

Re: What is active and passive NameNode in Hadoop?

Rising Star
Highlighted

Re: What is active and passive NameNode in Hadoop?

There is no such thing as a "passive" NameNode. Are you asking about the HA or non-HA configuration?

  1. In an HA configuration, there is
    1. Active NameNode that serves user requests.
    2. 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.
  2. In a non-HA configuration
    1. Primary NameNode that serves user requests.
    2. Secondary NameNode that generates periodic checkpoints. A secondary NameNode can never become the primary.

The terminology is unfortunately confusing.

View solution in original post

Don't have an account?
Coming from Hortonworks? Activate your account here