Subject: The mailing list for listmasters using Sympa
List archive
RE: [en@sympa] TTL refresh rate change in sympa.conf took 2 old rate refresh cycles before implementing new rate?
- From: "McLaren, Terry" <address@concealed>
- To: "Widerski, Betty" <address@concealed>, "address@concealed" <address@concealed>
- Subject: RE: [en@sympa] TTL refresh rate change in sympa.conf took 2 old rate refresh cycles before implementing new rate?
- Date: Mon, 21 Aug 2023 16:23:40 +0000
Hi Betty, et al – Don’t forget there are two ttl settings for membership inclusion, Admin > Edit List Config > Data Source Setup - …
#2 Inclusion timeout for message distribution (distribution_ttl) - is the more important setting since it will sync the remote subscriber list ‘before’ a message is sent to the list. Our default is 5 minutes (300sec), however, we allow the Privileged List Owners to change these settings to whatever time sync they feel is best for their members.
#1 Inclusion timeout (ttl) - Organizations with thousands of lists typically set #1 to a long interval to prevent unnecessary load on the servers (sympa, remote https, ldap,etc…) in an effort to improve efficiency of those services.
Hope this helps,
Terry McLaren
From: address@concealed <address@concealed>
On Behalf Of Widerski, Betty
I discovered the contractors who built our Sympa environment for some reason set the TTL refresh rate to 24 hours (86400 sec). This was unexpected and undesirable. I changed sympa.conf’s default_ttl to 1800 (30 minutes). I restarted services sympa and wwsympa Aug 17 22:14:44. After restart I checked several lists’ Data sources setup pages and confirmed their “Inclusions timeout (ttl)(default)” setting now said 1800. I expected this meant all lists would now refresh inclusions every 30 minutes.
However - it took two cycles of each list’s normal 24-hour refresh cycle before the 30 minute cycle started happening. For example, List A: - was refreshing at 12:18 daily - After the Aug 17 change/restart, it next refreshed Aug 18 12:18:07 - It next refreshed Aug 19 12:18:27 - Only then did it start refreshing every 30 minutes: 12:48, 13:18, etc.
Am I missing something about making sympa.conf changes take effect? This is 6.2.70 - the only thing I could find in documentation was that apparently the sympa.conf config is now “ttl” not “default_ttl”
Thanks Betty
Betty Widerski Cloud & Server Engineering – HBS Information Technology HARVARD BUSINESS SCHOOL Shad 108 N | address@concealed | T: 617.495.6642
|
-
[en@sympa] TTL refresh rate change in sympa.conf took 2 old rate refresh cycles before implementing new rate?,
Widerski, Betty, 08/21/2023
- RE: [en@sympa] TTL refresh rate change in sympa.conf took 2 old rate refresh cycles before implementing new rate?, McLaren, Terry, 08/21/2023
Archive powered by MHonArc 2.6.19+.