recommended number of listener_jobs
robrogers at mac.com
Wed Apr 6 11:10:00 PDT 2005
The reason I ask about this is that while benchmarking MogileFS, I've found that when forking off requests for any more than 29 - 30 child processes the mogilefs::backend starts failing to connect and throws this error:
MogileFS::Backend: couldn't connect to mogilefsd backend at /usr/lib/perl5/site_perl/5.8.5/MogileFS.pm line 91
Specifically, I've got a basic fork_and_work script which forks off a number of child processes than runs thru a specified number of runs.
All looks good upto children < 30. After 30 mogilefs starts rejecting requests(??). Is this weird?
On Wednesday, April 06, 2005, at 10:04AM, Brad Fitzpatrick <brad at danga.com> wrote:
>5 or 10 would probably work. We should make it automatic with a max cap
>of like 50 which if it reaches means it's the database that's loaded, and
>not the listener jobs.
>Here's our config:
># cat /etc/mogilefs/mogilefsd.conf
>daemonize = 1
>db_dsn = DBI:mysql:mogilefs:host=10.0.0.48
>db_user = mog
>db_pass = XXXXXXXXX
>conf_port = 7001
>listener_jobs = 30
>delete_jobs = 1
>replicate_jobs = 5
>mog_root = /mnt/mogilefs
>reaper_jobs = 0
>Though I'm not sure why we have mog_root defined... think that's old
>historic crap that we don't use anymore now that we're using HTTP mode.
>On Wed, 6 Apr 2005, Rob Rogers wrote:
>> Anybody have suggestions for number of listener_jobs for MogileFSD.
>> (or for that matter a good .conf file for Mogilefsd)
More information about the mogilefs