similar to: Solr connection timeout hardwired to 60s

On 4/4/2019 2:21 AM, Peter Mogensen via dovecot wrote: > What's the recommended way to handling timeouts on large mailboxes given > the hardwired request timeout of 60s in solr-connection.c: > > http_set.request_timeout_msecs = 60*1000; I'm a denizen of the solr-user at lucene.apache.org mailing list. For a typical Solr index, 60 seconds is an eternity. Most people aim

> I'm a denizen of the solr-user at lucene.apache.org mailing list. > [...] > Here's a wiki page that I wrote about that topic. This wiki is going > away next month, but for now you can still access it: > > https://wiki.apache.org/solr/SolrPerformanceProblems That's a great resource, Shawn. I am about to put together a test case to provide a comprehensive FTS

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

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

sorry... I got distracted half way and forgot to put a meaningfull subject so the archive could figure out the thread. - resending. On 4/14/19 4:04 PM, dovecot-request at dovecot.org wrote: >> Solr ships with autoCommit set to 15 seconds and openSearcher set to >> false on the autoCommit.? The autoSoftCommit setting is not enabled by >> default, but depending on how the index

Sorry to bump up an old thread. 2.3.11.3 already contains this patch and the error still gets generated.? Anything else we could try ? Scott On Wednesday, 19/08/2020 at 11:37 Josef 'Jeff' Sipek wrote: On Wed, Aug 19, 2020 at 17:03:57 +0200, Alessio Cecchi wrote: > Hi, > > after the upgrade to Dovecot 2.3.11.3, from 2.3.10.1, I see frequently > these errors from

https://www.lerctr.org/~ler/dovecot/doveadm-index-fts-debug.txt https://www.lerctr.org/~ler/dovecot/doveadm-index-fts-bt.txt I wish there was a way to set plugins {fts_solr = <blah>} from the command line :( but I turned it on globally for that run. On Wed, Jan 2, 2019 at 3:40 PM Stephan Bosch <stephan at rename-it.nl> wrote: > Oh, d'oh. I was looking for some solr debug

Hi, after the upgrade to Dovecot 2.3.11.3, from 2.3.10.1, I see frequently these errors from different users: Aug 18 11:02:35 Panic: indexer-worker(info at domain.com) session=<g71KISOttvS5LNVj:O3ahCyuZO18cYAAAEPCW+w>: file http-client-request.c: line 1232 (http_client_request_send_more): assertion failed: (req->payload_input != NULL) Aug 18 11:02:35 Error: indexer-worker(info at

On 19/08/2020 17:37, Josef 'Jeff' Sipek wrote: > On Wed, Aug 19, 2020 at 17:03:57 +0200, Alessio Cecchi wrote: >> Hi, >> >> after the upgrade to Dovecot 2.3.11.3, from 2.3.10.1, I see frequently >> these errors from different users: > It looks like this has been around for a while and you just got unlucky and > started seeing this now. Here's a quick

Sorry about that. My FreeBSD system automatically applied your patches and I assumed they were already part of the master. Unfortunately it still means the bug isn't resolved with these changes. On Wednesday, 02/09/2020 at 15:34 Josef 'Jeff' Sipek wrote: On Wed, Sep 02, 2020 at 15:07:37 -0400, Scott Q. wrote: > Sorry to bump up an old thread. > > 2.3.11.3 already

On 19.08.20 17:37, Josef 'Jeff' Sipek wrote: > On Wed, Aug 19, 2020 at 17:03:57 +0200, Alessio Cecchi wrote: >> Hi, >> >> after the upgrade to Dovecot 2.3.11.3, from 2.3.10.1, I see frequently >> these errors from different users: > It looks like this has been around for a while and you just got unlucky and > started seeing this now. Here's a quick

On 16.10.20 18:00, Scott Q. wrote: > This reminds me, the way I was able to reproduce this consistently was > by having large headers ( 100+ lines ). > > > On Friday, 16/10/2020 at 11:49 Patrik Peng wrote: > > On 19.08.20 17:37, Josef 'Jeff' Sipek wrote: > >> On Wed, Aug 19, 2020 at 17:03:57 +0200, Alessio Cecchi wrote: >>> Hi,

On 12/04/2019 12:09, Peter Mogensen via dovecot wrote: > 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

On 21/10/2020 16:44, Patrik Peng wrote: > On 16.10.20 18:34, Patrik Peng wrote: >> On 16.10.20 18:00, Scott Q. wrote: >>> This reminds me, the way I was able to reproduce this consistently >>> was by having large headers ( 100+ lines ). >>> >>> >>> On Friday, 16/10/2020 at 11:49 Patrik Peng wrote: >>> >>> On 19.08.20

On 4/4/19 6:57 PM, Peter Mogensen wrote: > > > 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

<!doctype html> <html> <head> <meta charset="UTF-8"> </head> <body> <div> <br> </div> <blockquote type="cite"> <div> On 14 April 2019 16:59 John Fawcett via dovecot < <a href="mailto:dovecot@dovecot.org">dovecot@dovecot.org</a>> wrote: </div>

Hi everyone Given that I am not an expert, I am doing tests with Solr, I installed following the guide but I have no benefits on the search, the search on the body on 28000 mails takes a few minutes and then goes to timeout. I had installed version 8.2.0 of solr then I thought that there is something not compatible with centos 7 so I installed version 7.7.0 as an example on the guide

On 14/04/2019 17:16, Peter Mogensen via dovecot wrote: > sorry... I got distracted half way and forgot to put a meaningfull > subject so the archive could figure out the thread. - resending. > > On 4/14/19 4:04 PM, dovecot-request at dovecot.org wrote: > >>> Solr ships with autoCommit set to 15 seconds and openSearcher set to >>> false on the autoCommit.? The

On 4/13/2019 4:29 AM, John Fawcett via dovecot wrote: > If this value was made configurable people could set it to what they > want. However the underlying problem is likely on solr configuration. The Jetty that is included in Solr has its idle timeout set to 50 seconds. But in practice, I have not seen this timeout trigger ... and if the OP is seeing a 60 second timeout, then the 50

On 22/10/2020 10:23, John Fawcett wrote: > On 21/10/2020 19:00, John Fawcett wrote: >> On 21/10/2020 16:44, Patrik Peng wrote: >>> On 16.10.20 18:34, Patrik Peng wrote: >>>> On 16.10.20 18:00, Scott Q. wrote: >>>>> This reminds me, the way I was able to reproduce this consistently >>>>> was by having large headers ( 100+ lines ).