Moosefs, dump meta on master?

Question

linux

Good luck to everyone outside the window.
I inherited a cluster on moosefs. Consists of several servers and one master. While I was sorting it out, I saw that the master makes a copy of the meta every hour, but it’s worth doing, for example, every 20 minutes or even more often.
After re-reading the Internet, I did not find how to force it to dump the meta.
Help me please.
Thanks

Answer 1

I don't use moosefs, but a quick look at the documentation made it clear that you can't decrease or increase the interval.
There is a recommendation to make a copy of the metadata in any convenient way during the intervals.

Yes, it is highly recommended to make additional backup of the metadata file. This provides a
worst case recovery option if, for some reason, the metalogger data is not useable for restoring
the master server (for example the metalogger server is also destroyed).
The master server flushes metadata kept in RAM to the metadata.mfs.back binary file every
hour on the hour (xx:00). So a good time to copy the metadata file is every hour on the half
hour (30 minutes after the dump) . This would limit the amount of data loss to about 1.5h of
data. Backing up the file can be done using any conventional method of copying the metadata
file – cp, scp, rsync, etc .
After restoring the system based on this backed up metadata file the most recently created files
will have been lost. Additionally files, that were appended to, would have their previous size,
86
which they had at the time of the metadata backup. Files that were deleted would exist again.
And files that were renamed or moved would be back to their previous names (and locations).
But still you would have all of data for the files created in the X past years before the crash
occurred.
In MooseFS Pro version, master followers flush metadata from RAM to the hard disk once an
hour. The leader master downloads saved metadata from followers once a day.

https://moosefs.com/Content/Downloads/moosefs-user...
www.it-recipes.com/articles/blog/122