Support Questions
Find answers, ask questions, and share your expertise

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

Explorer

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.

0 REPLIES 0