On 12/31/24 06:07, monochromec via Mailman-users wrote:
Further RCA reveals the fact that the archiver runner tries to archive the same message over and over again - hence the overhead during pipeline processing. The total # of attempts reaches well into five digits for a single message.
This is not directly related to the pipeline runner issues but they may have the same underlying cause. All the pipeline runner does is put the message in the archive queue. It's the archive runner that is doing all these retries.
However, the pipeline runner in processing the rfc_2369.py handler is also communicating with hyperkitty to get the values for the List-Archive: and Archived-At: headers.
You need to focus on the communication between mailman_hyperkitty and HyperKitty. If there are significant delays there, it could explain your pipeline runner issue.
Btw, I see https://gitlab.com/mailman/mailman/-/issues/1189 is also from you. I wondered at the time why you were trying to increase the number of pipeline runners which is not something that would normally be required.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan