search for: autowarm

...a test email with subject: aausdfrhy?tdwgyatrdf aausdfrhyetdwgyatrdf body: aausdfrhy?tdwgyatrdf aausdfrhyetdwgyatrdf i see a solr auto-scan, 2020-10-19 14:41:50.628 INFO (searcherExecutor-15-thread-1-processing-x:dovecot) [ x:dovecot] o.a.s.c.SolrCore [dovecot] Registered new searcher autowarm time: 1 ms 2020-10-19 14:41:50.634 INFO (qtp1533985074-18) [ x:dovecot] o.a.s.u.p.LogUpdateProcessorFactory [dovecot] webapp=/solr path=/update params={}{commit=} 0 155 2020-10-19 14:41:51.571 INFO (qtp1533985074-24) [ x:dovecot] o.a.s.u.p.LogUpdateProcessorFactory [dovecot] webapp=/solr...

...?tdwgyatrdf aausdfrhyetdwgyatrdf > ????body:??? aausdfrhy?tdwgyatrdf aausdfrhyetdwgyatrdf > > i see a solr auto-scan, > > ????2020-10-19 14:41:50.628 INFO? > (searcherExecutor-15-thread-1-processing-x:dovecot) [?? x:dovecot] > o.a.s.c.SolrCore [dovecot]? Registered new searcher autowarm time: 1 ms > ????2020-10-19 14:41:50.634 INFO? (qtp1533985074-18) [?? x:dovecot] > o.a.s.u.p.LogUpdateProcessorFactory [dovecot]? webapp=/solr > path=/update params={}{commit=} 0 155 > ????2020-10-19 14:41:51.571 INFO? (qtp1533985074-24) [?? x:dovecot] > o.a.s.u.p.LogUpdateProcessorF...

...gt; This thread says that dovecot is sending explicit commits.? I see explicit /update req. with softCommit and waitSearcer=true in a tcpdump. >> One thing >> that might be happening to exceed 60 seconds is an extremely long >> commit, which is usually caused by excessive cache autowarming, but >> might be related to insufficient memory.? The max heap setting on an >> out-of-the-box Solr install (5.0 and later) is 512MB.? That's VERY >> small, and it doesn't take much index data before a much larger heap >> is required. I run with SOLR_JAVA_MEM=&q...

...ve minutes would be good. Attempting to use a very short autoSoftCommit time will usually lead to problems. This thread says that dovecot is sending explicit commits. One thing that might be happening to exceed 60 seconds is an extremely long commit, which is usually caused by excessive cache autowarming, but might be related to insufficient memory. The max heap setting on an out-of-the-box Solr install (5.0 and later) is 512MB. That's VERY small, and it doesn't take much index data before a much larger heap is required. Thanks, Shawn

...;cite"> <div> This thread says that dovecot is sending explicit commits. One thing </div> <div> that might be happening to exceed 60 seconds is an extremely long </div> <div> commit, which is usually caused by excessive cache autowarming, but </div> <div> might be related to insufficient memory. The max heap setting on an </div> <div> out-of-the-box Solr install (5.0 and later) is 512MB. That's VERY </div> <div> small, and it doesn't take much i...

...gt; This thread says that dovecot is sending explicit commits.? I see explicit /update req. with softCommit and waitSearcer=true in a tcpdump. >> One thing >> that might be happening to exceed 60 seconds is an extremely long >> commit, which is usually caused by excessive cache autowarming, but >> might be related to insufficient memory.? The max heap setting on an >> out-of-the-box Solr install (5.0 and later) is 512MB.? That's VERY >> small, and it doesn't take much index data before a much larger heap >> is required. I run with SOLR_JAVA_MEM=&q...

...dovecot is sending explicit commits.? > I see explicit /update req. with softCommit and waitSearcer=true in a > tcpdump. > >>> One thing >>> that might be happening to exceed 60 seconds is an extremely long >>> commit, which is usually caused by excessive cache autowarming, but >>> might be related to insufficient memory.? The max heap setting on an >>> out-of-the-box Solr install (5.0 and later) is 512MB.? That's VERY >>> small, and it doesn't take much index data before a much larger heap >>> is required. > I run wi...

Looking further at tcpdumps of the Dovecot->Solr traffic and Solr metrics it doesn't seem like there's anything suspicious apart from the TCP windows running full and Dovecot backing of ... until it times out and close the connection. >From my understanding of how Dovecot operates towards Solr it will flush ~1000 documents towards Solr in /update request until it has traversed the

...ood.? Attempting to use > a very short autoSoftCommit time will usually lead to problems. > > This thread says that dovecot is sending explicit commits.? One thing > that might be happening to exceed 60 seconds is an extremely long > commit, which is usually caused by excessive cache autowarming, but > might be related to insufficient memory.? The max heap setting on an > out-of-the-box Solr install (5.0 and later) is 512MB.? That's VERY > small, and it doesn't take much index data before a much larger heap > is required. > > Thanks, > Shawn I looked into t...

I've since rebuilt/reconfig'd all parts of my setup from scratch; some good cleanup along the way. Atm, my entire system for send/recv, store/retrieve, + rules & search is working as I intend. Ok, mostly ... Except for this accented-character search mystery. I've got a _lot_ of mail with various languages in bodies, so _do_ need to get this sorted. > On 10/18/20 2:58 PM,