Nameservice nameservice1 has 2 NameNodes and 1 SecondaryNameNode(s)

[#1]

On a HA HDFS, I tried to add SecondaryNameNode. Here is what I face:

When I add the SecondaryNameNode role instance, I got "validation error":

Federated SecondaryNameNode secondarynamenode (mybigdata) is not configured with a Nameservice

When I configure nameservice as the nameservice of the HDFS cluster, I got "validation error" :

Nameservice nameservice1 has 2 NameNodes and 1 SecondaryNameNode(s)

So, how to correctly configure the SecondaryNameNode? What's the correct number of NameNode / SecondaryNameNode

Actually, we are getting around 200MB edit log in 1 month. Is is OK not to have SecondaryNameNode?

CDH 5.1, 5.2

[#2 · Accepted solution]

You do not need a SecondaryNameNode in HA. Please delete the role to
resolve your issue. You can read the HA Architecture at
http://archive.cloudera.com/cdh5/cdh/5/hadoop/hadoop-project-dist/hadoop-hdfs/HDFSHighAvailabilityWi...
to further understand how HA works.