With Hadoop 2.0, active and standby NameNodes were introduced. At any point, out of two NameNodes, one will always be in active state and other will be in standby state. The active NameNode is the one that's responsible for any client requests in the cluster. Standby NameNodes are slave nodes whose responsibility is to keep its state in sync with the active NameNode so that it can provide fast failover in the event of failover. However, what if one of the NameNodes fails? In that case, the NameNode would become non-HA. This means that NameNodes can only tolerate up to one failure. This behavior is the opposite of the core fault -tolerant behavior of Hadoop, which certainly can accommodate more than one failure of DataNodes in a cluster. Keeping that in mind, provisions of more than one standby NameNode was introduced in Hadoop 3. ...
United States
Great Britain
India
Germany
France
Canada
Russia
Spain
Brazil
Australia
Singapore
Hungary
Ukraine
Luxembourg
Estonia
Lithuania
South Korea
Turkey
Switzerland
Colombia
Taiwan
Chile
Norway
Ecuador
Indonesia
New Zealand
Cyprus
Denmark
Finland
Poland
Malta
Czechia
Austria
Sweden
Italy
Egypt
Belgium
Portugal
Slovenia
Ireland
Romania
Greece
Argentina
Netherlands
Bulgaria
Latvia
South Africa
Malaysia
Japan
Slovakia
Philippines
Mexico
Thailand