Shulou(Shulou.com)05/31 Report--

This article shares with you the content of an example analysis of the working mechanisms of fsimage and edits in Hadoop cluster management. The editor thinks it is very practical, so share it with you as a reference and follow the editor to have a look.

I.

Fsiamges files are usually metadata information for the entire cluster. It's a good memory every time it's modified, io.

So edits was introduced.

Files. Keep a record of each metadata modification and merge it periodically through Secondary Namenode.

II. Process

1.Secondary Namenode requests edits and fsimage to merge.

2.Namenode stops modifications to the edits file and generates the edits.new file, which stores changes to the metadata that occur during the merge

3.Secondary Namenode obtains edits file and fsimages file by http get

4.Secondary Namenode imports the requested fsimages file into memory and operates according to the edits file one by one to generate the fsimags.ckpt file.

5.Secondary Namenode sends the fsimages.ckpt file to Namenode through http post

After 6.Namenode accepts the fsimages.ckpt file, it replaces the original fsimages file and changes the edits.new file to the edits file, thus getting the new merged fsimages file and the smaller edits file.

Thank you for reading! This is the end of this article on "sample Analysis of the working Mechanism of fsimage and edits in Hadoop Cluster Management". I hope the above content can be of some help to you, so that you can learn more knowledge. if you think the article is good, you can share it out for more people to see!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.