[MM3-users] Re: Hyperkitty performance problem

[Tobias Diekershoff]

Hey all,




On 22.11.24 07:59, Tobias Diekershoff wrote:

thank you again for your input before - I wanted to update you all on the situation

so far we could not find the reason behind the problem.

In the meanwhile we have identified a symptom and could remove it, but not the root of the issue.

To rule out virtualization problems in our setup, we tried to migrate MM3 to a bare metal server in the data center. After importing the database for MM3 and Hyperkitty to the new postgresql server MM3 complained about

MultipleResultsFound: Multiple rows were found when one or none was required

With that error message--that does not occur on the running server--we found an old thread here on the mailing list [1] (Issue 657) and indeed we have multiple duplicates per mailing list on our server. Not one like in the linked thread, but some thousand (up to 150k) different per mailing list. Removing them returned the delivery of mails to the lists back to normal.

However the duplicates are added back to the listarchiver table for all archivers (mhonarc, hyperkitty, mail-archive and prototype) even though only hyperkitty is activated. We tried to add a constrain on the table to only allow one entry per list and archiver, but that caused the runner to fail and the message to be shunt.

Uncaught runner exception: (raised as a result of Query-invoked autoflush; consider using a session.no_autoflush block if this flush is occurring prematurely) (psycopg2.errors.UniqueViolation) duplicate key value violates unique constraint "workaround"

DETAIL:  Key (mailing_list_id, name)=(98, mhonarc) already exists.

hence we removed the constrain and now have a cron job running instead, that cleans out the duplicate database entries for the archivers.

Best,
  Tobias

I've checked that the workaround patch that mentioned in the issue 657 at gitlab [2] is in place. But it seems not to affect the issue we face. Should I update issue 657 with our problem/findings, or open a new issue for them? What puzzles us is that MM3 on the new server complained about these duplicates, were the running installation does not. They are "the same" (underlying Debian OS, installed packages, copied the config over). 1: https://lists.mailman3.org/archives/list/mailman-users%40mailman3.org/thread/PFVDFPGVWDTWFBTDS6DMYYWE6VE7PV3H/

2: https://gitlab.com/mailman/mailman/-/issues/657#note_1846487131

--
Tobias Diekershoff >>> System Hacker
Free Software Foundation Europe
Schönhauser Allee 6/7, 10119 Berlin, Germany | t +49-30-27595290
Registered at Amtsgericht Hamburg, VR 17030 | fsfe.org/support
OpenPGP-Key ID ... 0x25FE376FF17694A1
Fingerprint ...... 23EE F484 FDF8 291C BA09
                   A406 25FE 376F F176 94A1

OpenPGP_signature.asc
Description: OpenPGP digital signature

___________________________________________
Mailman's content filtering has removed the
following MIME parts from this message.

Content-Type: application/pgp-keys
    Name: OpenPGP_0x25FE376FF17694A1.asc

_______________________________________________
Mailman-users mailing list -- mailman-users@mailman3.org
To unsubscribe send an email to mailman-users-le...@mailman3.org
https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
Archived at: 
https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/QQDUMOIM7GRMGJ73KJLGSRTRPGGOL5RH/

This message sent to arch...@mail-archive.com