[Dovecot] [BUMP] When are search indexes updated?

[Dave Abrahams]

There are still quite a few mysteries in here.  Can you help me solve
them?

on Tue Dec 04 2012, Dave Abrahams <dave-AT-boostpro.com> wrote:

>>> 2. "doveadm search text SOMETHINGthatWONTbeFOUND" takes a long time and
>>>   finds stuff without crashing, but doesn't seem to create the
>>>   lucene-indexes/ directory in my mdbox, and it takes a long time the
>>>   next time around.  Is "doveadm search" intended to update the FTS
>>>   indexes if they're missing?
>>
>> Yes. It should trigger the same doveadm index -q code. Maybe you have
>> a (permission) problem connecting to indexer process. It should write
>> about that to stderr.
>
> Well, I'm not seeing anything like that :(
>
> I just stopped dovecot, removed my lucene-indexes, started dovecot up
> again, and issued "doveadm index -q / imap SEARCH body asdfg"
> It came back immediately with a prompt, there was no output, and I don't
> see an indexer-helper process.  In fact, the behavior is the same
> without "-q"
>
>>> 3. Performing a search on a large mailbox through IMAP takes a long time
>>>   the first time around, during which "top" shows the big cpu hog is
>>>   /opt/local/libexec/dovecot/indexer-worker, lucene-indexes/ is
>>>   created, and subsequent searches go quickly.  Nice!  Is there a
>>>   reasonably easy way to start such a search on all my mailboxes from
>>>   the command line by using doveadm or the preauth tunnel?
>>
>> doveadm index -q / imap SEARCH body asdfg
>
> This looks completely unlike anything I can find in "man doveadm-index";
> are you sure it's right?  I can delete any number of arguments after the
> "/" without seeming to affect its behavior.

-- 
Dave Abrahams
BoostPro Computing                  Software Development        Training
http://www.boostpro.com             Clang/LLVM/EDG Compilers  C++  Boost