From: Elliot F. <efi...@gm...> - 2011-08-13 03:10:29
|
On Wed, Aug 10, 2011 at 9:11 PM, Robert Sandilands <rsa...@ne...> wrote: > mfsmaster runs on the one chunkserver. The second chunkserver is a dedicated > chunkserver. The third chunkserver also runs mfsmetalogger. The second > chunkserver only has 2.5 million of the 96 million chunks so it is not > contributing much yet. > > On the master: > > The metadata is written on a SATA RAID1 volume. The chunks are stored on a > storage array that is connected via SAS. The only activity on the SATA > volume is the OS, metadata and local syslog logging. There is a second SAS > array that is used to stage files for deduplication. Part of the > deduplication process also moves it to the MooseFS volume. The server is a > dual quad-core 2 GHz Xeon and the average load is generally less than 5. The > deduplication uses a local mfsmount but is the only user of the mount. Although it seems this box should be able to handle the load with no problem, the obvious next step in stabilizing your cluster is to move the mfsmaster onto a box dedicated to the mfsmaster process. It also seems this would be a golden opportunity for the developers to take a look at your box and see why you are getting the client disconnects. If they could figure it out and tweak the code for your box, it would make their own cluster that much more stable. Elliot |