fts indexer stuck on very large plaintext messages
Hi,
I recently fts indexed a users mailbox with xapian which had 10-15 very large plaintext messages (>20Mb). The content of these messages was mostly a list of all files on a linux server (tripwire and backup reports).
The indexer-worker process was completely stuck processing these messages, cpu pegged at 100% running continuously for multiple days.
I was wondering if there is way to avoid this issue. It would be great if I could configure limits for the fts indexing process.
On 28/01/2024 10:21 EET p h via dovecot dovecot@dovecot.org wrote:
Hi,
I recently fts indexed a users mailbox with xapian which had 10-15 very large plaintext messages (>20Mb). The content of these messages was mostly a list of all files on a linux server (tripwire and backup reports).
The indexer-worker process was completely stuck processing these messages, cpu pegged at 100% running continuously for multiple days.
I was wondering if there is way to avoid this issue. It would be great if I could configure limits for the fts indexing process.
Hi!
fts-xapian is can be slow, can you try if fts-flatcurve gives better results? https://github.com/slusarz/dovecot-fts-flatcurve
it uses xapian too.
Aki
participants (2)
-
Aki Tuomi
-
p h