I can also add that I had top running while doing a doveadm index on
800 emails; doveadm took about 15 seconds to complete and in top I never
saw lucene-indexer (or lucene-worker) appear.
-Joe
On Sun, May 20, 2012 at 9:30 AM, Joe Beaubien joe.beaub...@gmail.comwrote:
On Sat, May 19, 2012 at
On 21.5.2012, at 17.12, Joe Beaubien wrote:
I can also add that I had top running while doing a doveadm index on
800 emails; doveadm took about 15 seconds to complete and in top I never
saw lucene-indexer (or lucene-worker) appear.
If you run doveadm index, the doveadm itself is doing all the
On Sat, May 19, 2012 at 10:16 PM, Timo Sirainen t...@iki.fi wrote:
On 20.5.2012, at 5.15, Joe Beaubien wrote:
Is it normal to not get output in the normal log files in this case, or
did
i miss something?
Before looking into it further, what's your doveconf -n output?
Here is the
Hi everyone,
I have a dovecot 2.1.6 setup with fts_lucene.
The lucene indexes get created/updated fine when I do a manual search thru
telnet.
However, if I run a webapp that uses the php::imap_search function, the
index never gets created/updated. I run indo the same problem with
thunderbird
Sorry for double-posting, but i forgot to mention something:
If I run php::imap_search() AFTER having manually updated the lucene
indexes (thru a telnet command), I see a HUGE gain in search performance
compared to before creating the lucene indexes (at least 1 order of
magnitude).
-Joe
On
On Sat, 2012-05-19 at 13:19 -0400, Joe Beaubien wrote:
I have a dovecot 2.1.6 setup with fts_lucene.
The lucene indexes get created/updated fine when I do a manual search thru
telnet.
So you run SEARCH TEXT or SEARCH BODY?
However, if I run a webapp that uses the php::imap_search
See answers inline.
I just want to add that i also tried the parameter fts_index_timeout = 10
in the plugin section. Unfortunately the logs never showed me any indexing
taking place. I also tried fts_index_timeout = 10s in case i had the
wrong syntax.
I also tried doveadm fts rescan -u my_user.
On 19.5.2012, at 23.40, Joe Beaubien wrote:
Ok, I enabled rawlog and noticed the code was only sending SEARCH FROM. I
modified it to also send a SEARCH TEXT and it triggered the fts index
update.
However, in my use case, that's not the search that needs to be done. The
search needed is
Answers inline.
On Sat, May 19, 2012 at 4:47 PM, Timo Sirainen t...@iki.fi wrote:
On 19.5.2012, at 23.40, Joe Beaubien wrote:
Ok, I enabled rawlog and noticed the code was only sending SEARCH
FROM. I
modified it to also send a SEARCH TEXT and it triggered the fts index
update.
On 20.5.2012, at 0.12, Joe Beaubien wrote:
You can run doveadm index -u user to get new mails indexed.
Awesome, this does seem to work.
2 last questions:
- Does it update both indexes (dovecot and fts) or only
dovecot.index.cache? I ask because I didn't see any index messages in log
On Sat, May 19, 2012 at 6:16 PM, Timo Sirainen t...@iki.fi wrote:
On 20.5.2012, at 0.12, Joe Beaubien wrote:
You can run doveadm index -u user to get new mails indexed.
Awesome, this does seem to work.
2 last questions:
- Does it update both indexes (dovecot and fts) or only
On 20.5.2012, at 5.15, Joe Beaubien wrote:
Is it normal to not get output in the normal log files in this case, or did
i miss something?
Before looking into it further, what's your doveconf -n output?
12 matches
Mail list logo
