From: Allen L. <lan...@gm...> - 2011-11-10 20:42:29
|
That would really bone a lot of configs, hardware config wise. My chunk servers all run with 512M of RAM, not the 16G or whatever I have in the master and the metalogger. It's "proper" that the chunkserver does the chunk serving job, and the metalogger does the metalogging job, and that the two aren't all mixed up into a single process/service. On 11/10/2011 2:28 PM, Steve wrote: > Sure its possible to start a metalogger your self. It just seems as though > it could have been part of the chunkservers > > > > > > > > > > > > -------Original Message------- > > > > From: Allen Landsidel > > Date: 10/11/2011 18:10:23 > > To: moo...@li... > > Subject: Re: [Moosefs-users] Lost all metadata on master w/ full disk > > > > What makes you think it can't? I don't think there's any reason you > > can't run mfsmetalogger on a chunk server, though I haven't tried. > > > > On 11/9/2011 4:28 PM, Steve wrote: > >> and why cant each chunkserver be a logger also by default >> -------Original Message------- >> From: Davies Liu >> Date: 09/11/2011 19:53:33 >> To: Nolan Eakins >> Cc: moo...@li... >> Subject: Re: [Moosefs-users] Lost all metadata on master w/ full disk >> In the mfsmaster, when dumping data to disk, it rename metadata.mfs.back >> to metadata.mfs.back.tmp first, then write to metadata.mfs.back, finally, > it > >> unlink metadata.mfs.back.tmp and metadata.mfs. >> If writing to metadata.mfs.back failed, we will get part of metadata, or >> damaged >> one, and previous metadata will be lost together. >> Why not writing to metadata.mfs.back.tmp first, if successfully, then > rename > >> it >> to metadata.mfs.back, and delete metadata.mfs ? I think this way is much >> safer. >> In the metalogger, it does not check the downloaded metadata, if it > download > >> a >> damaged one, then all the metadata will be lost. let metalogger keep > sereral > >> recently metadata may be safer. >> I will try to fix the above in my deployments, losing metadata is >> TOO UNACCEPTABLE. >> On Tue, Nov 8, 2011 at 7:24 AM, Nolan Eakins<no...@ea...> wrote: >>> I have a little server setup to give MooseFS a try. This server ran >>> out of disk space on its root partition a day or two ago. This >>> partition is where mfsmaster stored all of its data. Needless to say, >>> mfsmaster did something dumb and zeroed out all the metadata files >>> under /var/lib/mfs. It even looks like the metadata logger on another >>> machine was affected since it didn't store anything recoverable. >>> So my entire moosefs file tree is completely hosed now, all because >>> mfsmaster can't handle a full disk. >>> Other than this, I've been happy with MooseFS. >>> Regards, >>> Nolan > ----------------------------------------------------------------------------- > > >>> RSA(R) Conference 2012 >>> Save $700 by Nov 18 >>> Register now >>> http://p.sf.net/sfu/rsa-sfdev2dev1 >>> _______________________________________________ >>> moosefs-users mailing list >>> moo...@li... >>> https://lists.sourceforge.net/lists/listinfo/moosefs-users > > > ----------------------------------------------------------------------------- > > > RSA(R) Conference 2012 > > Save $700 by Nov 18 > > Register now > > http://p.sf.net/sfu/rsa-sfdev2dev1 > > _______________________________________________ > > moosefs-users mailing list > > moo...@li... > > https://lists.sourceforge.net/lists/listinfo/moosefs-users > > |