The mailing list for listmasters using Sympa

[Alex West <address@concealed>]

We are having issues with the load that eval_bouncers and purge_logs_table tasks put on the server. This is in combination with the ever ongoing sync_includes for over 21000 lists. We attempted to schedule the eval_bouncers and purge_logs_table tasks for a specific time by redefining the eval_bouncers.daily.task and purge_logs_table.daily.task like this:

title.gettext daily evaluation of bouncing users

/ACTION
stop ()

and similar for purge_logs_table.daily.task.

This stops the task manager from attempting to schedule these tasks on its own (or at least stops it from doing much of anything).

I then create files in /home/sympa/spool/task/ with modify times and a proper epoch date in the name to attempt to schedule these manually.

So for example,

-rw-r--r-- 1 sympa sympa 75 Jul 14 02:00 /address@concealed

to run the eval_bouncers at 2am.

This file creation happens around 12:15am

The content of the file created is:

title.gettext daily evaluation of bouncing users

/ACTION
eval_bouncers ()
stop ()

So in theory, the task should get executed at 2am, but what seems to happen is that it gets executed hours later. For instance, today it got executed at 11:22 am.

Jul 14 11:22:56 xxxxxx task_manager[26693]: notice Sympa::Spindle::ProcessTask::_execute() Running task Sympa::Task <date=1594717200;label=ACTION;model=eval_bouncers;context=*>

So my assumption is that the task_manager is so busy processing the constant onslaught of sync_includes, that it takes that long for it to get around to processing the task scheduled for 9 hours earlier.

Does this seem correct? Is task_manager really a serial operation like this, with no possibility of parallel processing of tasks?

Is there a better way to schedule a task so it runs at a specific time of day?

Thanks

--

Alex West - Operations

www.bossnine.com

www.pantek.com

216-344-1614 x301

Improving Your Speed to Market 

by Embracing Cloud and Linux Services