Re: [Moosefs-users] Metalogger issues

[Bán M. <ba...@vo...>]

Hi,

when I encountered that problem I have written and sent two metalog sync
scripts to this list which automatically restart the master if I
restart a log-server and download the actual mfsmetalog file. 
This solution with an other small patch about the instantaneous log
flush on the metaloggers eventuate a reliable metalogger.

Miklós

On Fri, 5 Nov 2010 12:04:14 -0600
Thomas S Hatch <tha...@gm...> wrote:

> I am looking at my mfsmetaloggers and I have some concerns, first, if
> I start the metaloggers before the master my changelog_ml.0.mfs stays
> empty, and I couldn't use the changelog yet anyway because the logger
> doesn't grab a copy of the metadata.mfs.bak file for a few hours.
> 
> Then the only times the changelog_ml.0.mfs file gets updated is when I
> restart the mfsmetalogger.
> 
> I am seeing this behavior on moosefs 1.6.17 and the yet unreleased
> 1.6.18.
> 
> This means that I am only getting information to the loggers when I
> restart mfsmetalogger and when the configured 24 hour download
> happens.
> 
> I am under the impression that the intended behavior is that when the
> metalogger starts it should grab the metadata.mfs file right away,
> and the changelog.0.mfs from the master, then the changelog_ml.0.mfs
> on the metalogger should be getting constant updates from the
> mfsmaster so that at any time an mfsmetarestore -a will recover a
> current working metadata.mfs file
> 
> Instead, I have gaps in my changelogs, I have to wait a very long
> time for metadata files and half the time mfsmetaresore -a fails.
> 
> Please help me understand what I am doing wrong with the metalogger.
> 
> -Thomas S Hatch