concept Secondary NameNode in category data

This is an excerpt from Manning's book Hadoop in Action.
By default, the Secondary NameNode[3] and the NameNode run on the same machine. For moderate size clusters (10 or more nodes), you should separate the Secondary NameNode into its own machine, the spec of which should be comparable to the NameNode. But, before going into how to set up a separate server as a Secondary NameNode, I should explain what the Secondary NameNode does and doesn’t do, and in turn some of NameNode’s underlying mechanics.
3 As of this writing, the Secondary NameNode is slated to be deprecated by version 0.21 of Hadoop, which should be released as this book goes to press. The Secondary NameNode will be replaced by a more robust design for warm standby. You should check the online documentation of the version of Hadoop you’re using to confirm whether it’s still using Secondary NameNode or not. The particular patch for this change is at https://issues.apache.org/jira/browse/HADOOP-4539.