search for: waitsearch

On 4/4/19 6:47 PM, dovecot-request at dovecot.org wrote: > For a typical Solr index, 60 seconds is an eternity. Most people aim > for query times of 100 milliseconds or less, and they often achieve > that goal. I'm pretty sure I get these while indexing, not querying. Apr 04 16:44:50 host dovecot[114690]: indexer-worker(me at example.com): Error: fts_solr: Indexing failed: Request

...t; > > <lst name="responseHeader"> > <int name="status">0</int> > <int name="QTime">0</int> > </lst> > </response> And Solr receives it. Your tcpdump doesn't show <commit softCommit="true" waitSearcher="true"/> being sent though. Do you see it being sent anywhere? Does it make the mails visible if you run it yourself? Or if you run hard commit? : curl http://<host>:8983/solr/update?commit=true -------------- next part -------------- An HTML attachment was scrubbed... URL: &...

...P answer: ============================================== POST /solr/dovebody/update HTTP/1.1 Host: localhost:8983 Date: Wed, 10 Apr 2019 14:22:29 GMT Expect: 100-continue Content-Length: 47 Connection: Keep-Alive Content-Type: text/xml HTTP/1.1 100 Continue <commit softCommit="true" waitSearcher="true"/> ================================================ ... in contrast to the first softCommit on the connection: ================================================ POST /solr/dovebody/update HTTP/1.1 Host: localhost:8983 Date: Wed, 10 Apr 2019 14:20:53 GMT Expect: 100-continue C...

...gt;>> ?<int name="status">0</int> >>> ?<int name="QTime">0</int> >>> </lst> >>> </response> >> >> And Solr receives it. Your tcpdump doesn't show <commit >> softCommit="true" waitSearcher="true"/> being sent though. Do you see >> it being sent anywhere? > > Yes: > > ################### TCPDUMP ################################### > POST /solr/dovecot/update HTTP/1.1 > Host: localhost:8983 > Date: Mon, 28 May 2018 10:18:05 GMT > Expect:...

...== > POST /solr/dovebody/update HTTP/1.1 > Host: localhost:8983 > Date: Wed, 10 Apr 2019 14:22:29 GMT > Expect: 100-continue > Content-Length: 47 > Connection: Keep-Alive > Content-Type: text/xml > > HTTP/1.1 100 Continue > > <commit softCommit="true" waitSearcher="true"/> > ================================================ ....

...lt.? I think it is. > >> If there is an issue on initial indexing, where you are not really >> concerned about qucik visibility but just getting things into the index >> efficiently, a better approach would be for dovecot plugin not to send >> any commit or softCommit (or waitSearcher either) and that should speed >> things up. You'd need to configure solr with a long autoSoftCommit >> maxTime and a reasonable autoCommit maxTime, which you could then >> reconfigure when the load was done. > > Solr ships with autoCommit set to 15 seconds and openSear...

...;responseHeader"> >> ?<int name="status">0</int> >> ?<int name="QTime">0</int> >> </lst> >> </response> > > And Solr receives it. Your tcpdump doesn't show <commit > softCommit="true" waitSearcher="true"/> being sent though. Do you see it > being sent anywhere? Yes: ################### TCPDUMP ################################### POST /solr/dovecot/update HTTP/1.1 Host: localhost:8983 Date: Mon, 28 May 2018 10:18:05 GMT Expect: 100-continue Content-Length: 47 Connection:...

...is the case by default. I think it is. > If there is an issue on initial indexing, where you are not really > concerned about qucik visibility but just getting things into the index > efficiently, a better approach would be for dovecot plugin not to send > any commit or softCommit (or waitSearcher either) and that should speed > things up. You'd need to configure solr with a long autoSoftCommit > maxTime and a reasonable autoCommit maxTime, which you could then > reconfigure when the load was done. Solr ships with autoCommit set to 15 seconds and openSearcher set to false on...

...lt;/div> <div> >> concerned about qucik visibility but just getting things into the index </div> <div> >> efficiently, a better approach would be for dovecot plugin not to send </div> <div> >> any commit or softCommit (or waitSearcher either) and that should speed </div> <div> >> things up. You'd need to configure solr with a long autoSoftCommit </div> <div> >> maxTime and a reasonable autoCommit maxTime, which you could then </div> <div> >&gt...

...are designed to make documents visible to searches quickly. If there is an issue on initial indexing, where you are not really concerned about qucik visibility but just getting things into the index efficiently, a better approach would be for dovecot plugin not to send any commit or softCommit (or waitSearcher either) and that should speed things up. You'd need to configure solr with a long autoSoftCommit maxTime and a reasonable autoCommit maxTime, which you could then reconfigure when the load was done. If you're using dovecot built from source code it should be possible to test that by some...

On 21 May 2018, at 14.11, kadafax at gmail.com wrote: > > Le 21/05/2018 ? 12:38, Aki Tuomi a ?crit : >> can you try turning on pluign { fts_enforced = yes } and repeat your test? > > Same (wrong) result: > 1. Send an email with "too6Ouka" in the body > > 2. Search against "too6Ouka": > # doveadm search -u username mailbox INBOX body too6Ouka