The mailing list for listmasters using Sympa

[Gonzalo Palacios Goicolea <address@concealed>]

Hi Sabine

Thanks for the hint, pulling the thread I solved it. The question was that for each list its source is a local file (about 300), one of the servers of the pool created about 100 task for updating it. Each time it's updated from file, there is one field of the subscriber_table that is updated for all the list subscribers, generating too much noise at the database.

Just removing all those repetitive tasks from the spool solved the issue.

Thanks again and best regards,

Gonzalo

El 29/01/2020 a las 8:50, Lorenz, Sabine (SCC) escribió:

Hi Gonzalo,

 

in version 6.2.16 there’s the parameter „inclusions timeout (ttl)“ which regulates how long the data that is included during inclusion is stored.

As far as I know, this parameter also regulates that the data is not included again during this period.

This applies to all include parameters and thus also to file inclusion.

 

If this parameter still exists in this form in version 6.2.52, this could be the parameter you are looking for.

 

Best regards,

Sabine

 

 

 

 

Von: address@concealed [mailto:address@concealed] Im Auftrag von Gonzalo Palacios Goicolea
Gesendet: Dienstag, 28. Januar 2020 16:44
An: address@concealed
Betreff: [sympa-users] include_file interval

 

Hi All,

After upgrading sympa from 6.2.16 to 6.2.52 we've noticed that the use of database is bigger. It seems that the origin are the tasks that manage the inclusion of subscribers from local files (include_file). Every time one of this tasks is run, the field "inclusion_ext_subscriber" on subscriber_table is updated for all the list subscribers. Before upgrading I think these tasks were done on a file, but now it's updated to the database. My question is, how can I manage the time interval between each update?

Now every list is updated on a non-regular basis, but about every 15-25 minutes:

Jan 28 03:48:48 listas4 task_manager[2821]: notice Sympa::Spindle::ProcessRequest::_twist() Processing Sympa::Request <action="include;address@concealed;role=member> Jan 28 04:05:49 listas4 task_manager[2821]: notice Sympa::Spindle::ProcessRequest::_twist() Processing Sympa::Request <action="include;address@concealed;role=member> Jan 28 04:26:11 listas4 task_manager[2821]: notice Sympa::Spindle::ProcessRequest::_twist() Processing Sympa::Request <action="include;address@concealed;role=member> Jan 28 04:46:19 listas4 task_manager[2821]: notice Sympa::Spindle::ProcessRequest::_twist() Processing Sympa::Request <action="include;address@concealed;role=member> Jan 28 05:07:19 listas4 task_manager[2821]: notice Sympa::Spindle::ProcessRequest::_twist() Processing Sympa::Request <action="include;address@concealed;role=member> Jan 28 05:34:23 listas4 task_manager[2821]: notice Sympa::Spindle::ProcessRequest::_twist() Processing Sympa::Request <action="include;address@concealed;role=member> Jan 28 05:54:25 listas4 task_manager[2821]: notice Sympa::Spindle::ProcessRequest::_twist() Processing Sympa::Request <action="include;address@concealed;role=member> Jan 28 06:14:24 listas4 task_manager[2821]: notice Sympa::Spindle::ProcessRequest::_twist() Processing Sympa::Request <action="include;address@concealed;role=member> Jan 28 06:34:44 listas4 task_manager[2821]: notice Sympa::Spindle::ProcessRequest::_twist() Processing Sympa::Request <action="include;address@concealed;role=member> Jan 28 06:57:44 listas4 task_manager[2821]: notice Sympa::Spindle::ProcessRequest::_twist() Processing Sympa::Request <action="include;address@concealed;role=member> Jan 28 07:15:01 listas4 task_manager[2821]: notice Sympa::Spindle::ProcessRequest::_twist() Processing Sympa::Request <action="include;address@concealed;role=member> Jan 28 07:35:39 listas4 task_manager[2821]: notice Sympa::Spindle::ProcessRequest::_twist() Processing Sympa::Request <action="include;address@concealed;role=member> Jan 28 07:43:18 listas4 task_manager[2821]: notice Sympa::Spindle::ProcessRequest::_twist() Processing Sympa::Request <action="include;address@concealed;role=member> Jan 28 08:01:34 listas4 task_manager[2821]: notice Sympa::Spindle::ProcessRequest::_twist() Processing Sympa::Request <action="include;address@concealed;role=member> Jan 28 08:25:30 listas4 task_manager[2821]: notice Sympa::Spindle::ProcessRequest::_twist() Processing Sympa::Request <action="include;address@concealed;role=member> Jan 28 08:54:51 listas4 task_manager[2821]: notice Sympa::Spindle::ProcessRequest::_twist() Processing Sympa::Request <action="include;address@concealed;role=member> Jan 28 09:05:43 listas4 task_manager[2821]: notice Sympa::Spindle::ProcessRequest::_twist() Processing Sympa::Request <action="include;address@concealed;role=member> Jan 28 09:29:47 listas4 task_manager[2821]: notice Sympa::Spindle::ProcessRequest::_twist() Processing Sympa::Request <action="include;address@concealed;role=member> Jan 28 09:49:13 listas2 task_manager[2832]: notice Sympa::Spindle::ProcessRequest::_twist() Processing Sympa::Request <action="include;address@concealed;role=member>

Thanks and best regards

--

Gonzalo Palacios Goicolea
U.T de Infraestructura de Equipos Centrales
Tecnologías de la Información
Universidad Autónoma de Madrid • Campus de Cantoblanco

 

--
Gonzalo Palacios Goicolea
U.T de Infraestructura de Equipos Centrales
Tecnologías de la Información
Universidad Autónoma de Madrid • Campus de Cantoblanco
c/ Francisco Tomás y Valiente, n° 11, Edificio B de la EPS – TI-208 - 28049, Madrid
Tel.: 91497 2368 – address@concealed - www.uam.es LinkedIn | Twitter | Facebook | Youtube
¿Eres de la Autónoma? Hazte AlumniUAM     Antes de imprimir este correo piense si es necesario.Cuidemos el medioambiente.