Mogilefs configuration meanings

64 views
Skip to first unread message

Zubin

unread,
Oct 23, 2008, 5:13:54 PM10/23/08
to mogile
Hey guys, I've setup Mogilefs successfully but I've used most of the
default parameters.

The version of Mogilefs i set up is 2.20

I was looking through various howto's and noticed a lot of
configuration parameters that I don't have in my configs and I was
wondering if someone can give me a quick explanation of the following
configuration parameters and if they are still valid for 2.20.



/etc/mogilefs/mogilefs.conf

listener_jobs 5
delete_jobs = 1
replicate_jobs = 5
reaper_jobs = 1
monitor_jobs = 1
fsck_jobs = 1
daemonize = 1
mog_root = /mnt/mogilefs



etc/mogstored/mogstored.conf

maxconns = 10000



/etc/mogilefs/mogtool.conf

overwrite = 1
chunksize = 32M
receipt = ad...@bigmaps.com
verify = 1
concurrent = 3


A quick explanation of each of these parameters would be greatly
appreciated, particularly the mogilefs.conf ones

Thanks,

Zubin Parihar

dormando

unread,
Nov 2, 2008, 1:53:39 AM11/2/08
to mogile

On Thu, 23 Oct 2008, Zubin wrote:

> /etc/mogilefs/mogilefs.conf
>
> listener_jobs 5
> delete_jobs = 1
> replicate_jobs = 5
> reaper_jobs = 1
> monitor_jobs = 1
> fsck_jobs = 1

These control the number of the various workers running... leave the last
3 at one, and tune the rest upward if necessary. ie; if deletes are
lagging, add more delete workers. if your requests aren't being processed
very fast, you might need more listeners (queryworkers).

> daemonize = 1

whether or not to background mogilefsd.

> mog_root = /mnt/mogilefs

meh.

>
>
> etc/mogstored/mogstored.conf
>
> maxconns = 10000

obvious. :P

>
>
> /etc/mogilefs/mogtool.conf
>
> overwrite = 1
> chunksize = 32M
> receipt = ad...@bigmaps.com
> verify = 1
> concurrent = 3

Useless unless you're using mogtool to store very large backups of
files... easy enough to just ignore this.

These really aren't documented in the mailing list history or wiki
anywhere?

-Dormando

Gavin

unread,
Nov 2, 2008, 12:56:29 PM11/2/08
to mog...@googlegroups.com
> These really aren't documented in the mailing list history or wiki
> anywhere?

Which wiki is the best to update /look for information?

dormando

unread,
Nov 3, 2008, 2:47:05 AM11/3/08
to mog...@googlegroups.com
>> These really aren't documented in the mailing list history or wiki
>> anywhere?
>
> Which wiki is the best to update /look for information?

Uhhhm. Embarassing. We should be moving to the google pages wiki. Anyone
want to finish moving pbwiki over there so we can retire it?

-Dormando

Reply all
Reply to author
Forward
0 new messages