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.

Why fsImage saved in name node and secondary name node differs while using hdfs dfsadmin -saveNamespace?

Why fsImage saved in name node and secondary name node differs while using hdfs dfsadmin -saveNamespace?

New Contributor

current latest fsimage in both name node and secondary name node directory is fsimage_0000000000000016517

after using

hdfs dfsadmin -safemode enter

hdfs dfsadmin -saveNamespace

hdfs dfsadmin -safemode leave

latest fsImage in name node is fsimage_0000000000000016522 & latest fsImage in name node is fsimage_0000000000000016520

why there is difference in that?

upto my understanding hdfs dfsadmin -saveNamespace command should save latest fsImage in both name node and secondary name node.