Re: fts-flatcurve 2.4.4: after "doveadm fts optimize" a mailbox stops indexing new mail (empty current.<id> shard, missing iamglass)
Michael Slusarz via dovecot <[email protected]>
| Newsgroups | gmane.mail.imap.dovecot |
|---|---|
| Message-ID | <[email protected]> |
> On 08/07/2026 10:22 AM MDT Ihor Rusyn via dovecot <[email protected]> wrote: > > Hello, > > "doveadm fts optimize" leaves the mailbox in a state where no new mail can > be > indexed. The existing index survives and searches over already-indexed mail > keep > working, so the damage is invisible until the next message arrives. > > Version: 2.4.4 (8b687aa65c), packaged in a container image > FTS: fts_flatcurve, substring_search = yes, min_term_size default > (2) > fts_autoindex = yes, fts_search_add_missing = yes > Index store: NFSv3 (rsize/wsize 32768, local_lock=none) > Mail store: NFSv3, maildir [snip] I cannot reproduce this, probably due to some combination of NFS latency and semantics. (Xapian itself notes that NFS operation can be problematic. https://xapian.org/docs/admin_notes.html) It's likely fixed by adding fts_flatcurve_xapian_refresh() in fts_flatcurve_xapian_optimize_box_do(), but I am unable to verify. michael _______________________________________________ dovecot mailing list -- [email protected] To unsubscribe send an email to [email protected]