Re: [Moosefs-users] mfsmaster performance and hardware

[Robert S. <rsa...@ne...>]

Or I can log into the system on the hour and see if two processes named 
mfsmaster exists. In my case it does not which may indicate that fork() 
is failing.

Running strace on the single instance of mfsmaster also indicates it is 
busy writing to a file and I can see the the following files:

-rw-r-----  1 daemon daemon  11G Aug  8 18:02 metadata.mfs.back
-rw-r-----  1 daemon daemon  11G Aug  8 17:02 metadata.mfs.back.tmp

metadata.mfs.back.tmp was deleted several seconds later.

iostat -x also indicates 100% utilization on the volume where the 
meta-data is stored with a very high number of writes.

This leaves me with:

1. Get a faster disk for doing the metadata backups on (SSD?)
2. Figure out why fork() is failing

mfsmaster is the only process using more than 5 GB of RAM on the machine 
(32.6 GB). mfschunkserver uses 4.8 GB. No processes seems to be locking 
any significant amount of memory. The number of processes created per 
second < 1. The machine has 64 GB of RAM.

Robert

On 8/8/11 3:46 PM, Elliot Finley wrote:
> On Mon, Aug 8, 2011 at 1:33 PM, Elliot Finley<efi...@gm...>  wrote:
>> Attached is a patch for filesystem.c that will indicate in your log
>> file whether or not the fork was successful.  I'd be curious to see
>> the results.
> Sorry, that last patch has a small problem, attached is the correct one.
>
> Elliot