Displaying 20 results from an estimated 500 matches similar to: "Solr connection timeout hardwired to 60s"
2019 Apr 12
2
Solr connection timeout hardwired to 60s
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
2019 Apr 10
0
Solr connection timeout hardwired to 60s
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
2018 May 28
2
Bug: Dovecot index loosing sync with FTS despite "fts_autoindex = yes"
On 28 May 2018, at 13.28, kfx <kadafax at gmail.com> wrote:
>
>
>> Especially what is in the "fts" header vs. "next uid" header? Does the UID in "fts" header keep changing every time you save a new mail? I suppose it will.
>
> Diff between 2 emails:
> next uid = 30104 | next uid = 30105
> last_indexed_uid = 30103 |
2019 Apr 13
3
Solr connection timeout hardwired to 60s
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
2019 Apr 14
1
[PATCH] Re: Solr connection timeout hardwired to 60s
<!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>
2018 May 28
1
Bug: Dovecot index loosing sync with FTS despite "fts_autoindex = yes"
On 28/05/2018 13:23, kfx wrote:
> On 28/05/2018 13:04, Timo Sirainen wrote:
>> On 28 May 2018, at 13.28, kfx <kadafax at gmail.com
>> <mailto:kadafax at gmail.com>> wrote:
>>>
>>>
>>>> Especially what is in the "fts" header vs. "next uid" header? Does
>>>> the UID in "fts" header keep changing
2019 Apr 14
2
Solr connection timeout hardwired to 60s
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
2019 Apr 13
0
Solr connection timeout hardwired to 60s
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
2018 May 24
2
Bug: Dovecot index loosing sync with FTS despite "fts_autoindex = yes"
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
2019 Apr 14
0
[PATCH] Re: Solr connection timeout hardwired to 60s
On 13/04/2019 17:16, Shawn Heisey via dovecot wrote:
> 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
2019 Apr 14
0
Solr connection timeout hardwired to 60s
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
2020 Nov 13
2
dovecot fts-solr + solr 8.7.0 upgrade: "Indexing failed: 401 Unauthorized" + "Transaction commit failed: FTS transaction commit failed: backend deinit" ?
I've built a new dovecot + fts-solr instance; I've now picked up & am running the recently released solr 8.7.0.
In a test account, I've one message -- in the 'Drafts' folder.
On exec of fts 'index'
doveadm index -u testuser at example.com -q '*'
I get a
401 unauthorized
indexing failure, only for the one dir+message in 'Drafts',
2020-11-13
2019 Apr 04
4
Solr connection timeout hardwired to 60s
Hi,
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;
/Peter
2018 May 28
0
Bug: Dovecot index loosing sync with FTS despite "fts_autoindex = yes"
On 28/05/2018 13:04, Timo Sirainen wrote:
> On 28 May 2018, at 13.28, kfx <kadafax at gmail.com
> <mailto:kadafax at gmail.com>> wrote:
>>
>>
>>> Especially what is in the "fts" header vs. "next uid" header? Does
>>> the UID in "fts" header keep changing every time you save a new mail?
>>> I suppose it will.
2019 Apr 14
1
dovecot Digest, Vol 192, Issue 52
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 was created, Solr might try to
>> set autoSoftCommit to 3 seconds ... which is WAY too short.
I just run with the default. 15s
2019 Apr 04
0
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
2018 Jun 07
3
FTS Solr errors using doveadm
Solr 7 returns JSON by default but fts_solr requires XML.
Would be good to have wt=xml added to the query to force it to xml all the time, this would prevent errors if solr has
not had xml set as default for index.
Dovecot 2.2.36
Centos 6
*Doveadm Request:*
doveadm search -u caroline at covermg.com TEXT smith
doveadm(caroline at covermg.com): Error: fts_solr: Invalid XML input at 1:0: not
2017 Nov 30
2
My Solr FTS problem
I am testing the solr FTS following the guide here:
http://things.m31.ch/?p=379
Now I am having problem when I try to test:
# doveadm -v? index -u fail2ban at mydomain.com Inbox
doveadm(fail2ban at mydomain.com): Error: fts_solr: Invalid XML input at
1:0: not well-formed (invalid token) (near: {
? "responseHeader":{
??? "status":0,
??? "QTime":0,
???
2017 Dec 14
4
auth_policy in a non-authenticating proxy chain
Hi,
I was looking into the new Authentication Policy feature:
https://wiki2.dovecot.org/Authentication/Policy
I had kinda hoped that I would be able to enfore this in a proxy running
in front of several backends. This proxy does not authenticate. It use
"nopassword".
But I realize that the "succes" reported in the final authpolicy req.
(command=report) is not what is
2019 Sep 03
3
dsync and altpath on shared storage.
On 9/2/19 3:03 PM, Sami Ketola wrote:
>> On 2 Sep 2019, at 15.25, Peter Mogensen via dovecot <dovecot at dovecot.org> wrote:
...
>> Is there anyway for dsync to avoid moving Gigabytes of data for could
>> just be "moved" by moving the mount?
>
>
> Not tested but you can probably do something like this in the target server:
>
> doveadm backup -u