On Sun, Feb 5, 2023 at 8:32 PM Mark Sapiro <mark@msapiro.net> wrote:
On 2/5/23 01:13, Odhiambo Washington wrote:
So in my case, I should at least increase the value of HYPERKITTY_JOBS_UPDATE_INDEX_LOCK_LIFE to, say, 1800?
It probably isn't even set in your case and defaults to 900 if it isn't set.
I have never seen this config option in any of the settings files and so believe that no one has it set - except the DEVs, maybe.
Yes, you can set it to a larger value. If your archive search engine is woosh and your archive is even moderately large, 1800 probably isn't nearly enough.
Yes, my archive search engine is whoosh. And my archives size is 2.5GB+ For starters I will make it 3600 and observe next time.
There was no indication of timing in your OP, but you should determine when that cron job started and when the error was reported. The difference is the absolute minimum you should set for HYPERKITTY_JOBS_UPDATE_INDEX_LOCK_LIFE, but you should add some margin to that.
Sadly I deleted the email. I will have to determine those aspects next time. I need to make a request for a small improvement on the documentation at: https://docs.mailman3.org/en/latest/install/virtualenv.html#cron-jobs-for-ma... The problem I am facing (the subject of this thread is that of a race between the "monthly hyperkitty update_and_clean_index" job and the hourly "hyperkitty update_index job" Would it be possible to add such details to the section, so that it is clear what the corn jobs do and perhaps what can lead to such race conditions (if that's not too much to ask)?
-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)