Re: [Moosefs-users] mfs-master[4166]: CS(10.10.10.10) packet too long (226064141/50000000)

[Fabien G. <fab...@gm...>]

Hi all,

2010/6/29 Michał Borychowski <mic...@ge...>

>   * 'mfsmaster' process on master : 4.9 GB (64 bits recompilation required
> : the 32 bits version of mfsmaster crashed without a message when it came to
> 4 GB)
> * 'mfschunkserver' process on chunkservers : 580 MB
>
> [MB] 32bit machines are not capable of addressing more than 4GB, so that
> was quite a normal behaviour.
>
> Regarding memory please have a look at this FAQ entry:
>
> http://www.moosefs.org/moosefs-faq.html#cpu – there is information about
> the cpu loads and ram usage. Keep in mind that RAM depends on the total
> number of files and folders (not on their size) and CPU load in mfsmaster
> depends on amount of operations which take place in the filesystem.
>

Yes I read that page (actually I read every pages of moosefs.org to really
understand how it works !). It's just a mistake I made to compile it on a 32
bits platform.
But maybe you could tell the dev team that in case of memory allocation
failure, mfsmaster crashes without a message... well, if we consider that
"segmentation fault" is not a real error message :-)



> Maybe later, we'd like to use it for webhosting. But since LOCK is not
> supported, it's not yet possible.
>
> [MB] What for do you need LOCK for webhosting?
>

Dynamic websites, writing information to files. Several web servers using
the same MooseFS could try to write to the same file in the same time.


Fabien