Displaying 20 results from an estimated 600 matches similar to: "Solr connection timeout hardwired to 60s"
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
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 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>
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 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 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 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
2017 Dec 01
1
Do we really need Solr commit as cronjob?
I am testing Solr FTS on dovecot. Read online that some suggested to run
cronjob commit every minute, and optimize once a day.
I am using Solr 7.1.0 and I see some configurations:
In /etc/default/solr.in.sh:
#SOLR_OPTS="$SOLR_OPTS -Dsolr.autoSoftCommit.maxTime=3000"
#SOLR_OPTS="$SOLR_OPTS -Dsolr.autoCommit.maxTime=60000"
Also in solrconfig.xml:
??? <autoCommit>
2018 Mar 05
1
Re: [enhancement] fts-solr low performance
>Hi,
>
>we have activated fts-solr about a week ago and immediately started to
>experience really *low* performance with MOVE and EXPUNGE commands.
>After several days of googling, tcpdumping and straceing i was able to
>find and resolve the problem.
>
>We are using Dovecot 2.2.27 from Debian Jessie (jessie-backports),
>which is doing a soft commit in solr after
2019 Apr 04
2
Solr connection timeout hardwired to 60s
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
2019 Apr 23
3
SolrCore 'dovecot' is not available due to init failure: fieldType 'text_general' not found in the schema
https://wiki.dovecot.org/Plugins/FTS/Solr
Only offers a solr-7.7.0 solrconfig.xml, does it apply to solr-8.0.0?
On Tue, Apr 23, 2019 at 11:18 AM luckydog xf <luckydogxf at gmail.com> wrote:
> Here is solrconfig.xml, I removed comments.
> --------------------
>
> <?xml version="1.0" encoding="UTF-8"?>
> <config>
>
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
2017 Mar 05
0
[enhancement] fts-solr low performance
Hi,
we have activated fts-solr about a week ago and immediately started to
experience really *low* performance with MOVE and EXPUNGE commands.
After several days of googling, tcpdumping and straceing i was able to
find and resolve the problem.
We are using Dovecot 2.2.27 from Debian Jessie (jessie-backports),
which is doing a soft commit in solr after every MOVE or EXPUNGE
command -
2019 Apr 23
2
SolrCore 'dovecot' is not available due to init failure: fieldType 'text_general' not found in the schema
Hello, it seems an mismatch of schema file provided by dovecot-2.3.5.2
[root at mail conf]# pwd
/var/solr/data/dovecot/conf
# Below solrconfig.xml is from Solr-8.0.0.
[root at mail conf]# grep text_general solrconfig.xml
<str name="queryAnalyzerFieldType">text_general</str>
field types. Text content will be indexed as "text_general" as
<str
2019 Apr 23
0
SolrCore 'dovecot' is not available due to init failure: fieldType 'text_general' not found in the schema
Here is solrconfig.xml, I removed comments.
--------------------
<?xml version="1.0" encoding="UTF-8"?>
<config>
<luceneMatchVersion>8.0.0</luceneMatchVersion>
<lib dir="${solr.install.dir:../../../..}/contrib/extraction/lib"
regex=".*\.jar"/>
<lib dir="${solr.install.dir:../../../..}/dist/"
2006 Feb 23
2
ActiveRecords question
I need to turn off and on the autocommit in MySql is there a method in
active records that allows me to do this?
or
is there a method which allows me to type in the pure mysql code
"set autocommit=0"
Thanks.
--
Posted via http://www.ruby-forum.com/.
2018 Dec 30
3
Solr
Hi Daniel,
I am on Archlinux. Anyway, I adapted the scripts.
2 questions:
1 - It looks like we are not on the same version . I am on 7.5.0. Which
version are you running ?
2 - Your conf shows that you let managed-schema but deleted schema.xml.
What is the meaning of each ?
Thank you
On 2018-12-22 00:19, Daniel Miller wrote:
> Joan,
>
> The reason for dropping squat, I'm
2009 Jan 13
2
Connect multiple DB in rails project using AR
Dear all
I have a rails project which database connection is defined in
database.yml. There is a table call "servers" which have about 40
records, which is a collection of database setting (i.e. Server.name,
Server.port, Server.host)
I know the way to establish multiple connection as below...
class A < ActiveRecord::Base
end
A.establish_connection(a) # a is the database config
2006 Jan 10
2
Transactions with multiple databases
hi,
i have problem with transactions and multiple databases.
Object1 and Object2 are two different models/databases with different
connections, when i use only
one model:
Object1.transaction do
object1.value1 = "123456"
object1.save
do_some_error
end
it''s ok, error is produced, nothing is commited and database is unchanged.
when i use 2 models, described at
2015 Apr 14
1
Updating Solr - was Disk space usage with mdbox
So with "fts_autoindex=yes" enabled in plugins, is there anything I
should be running regularly, other than the expunge/purge, to ensure
Solr indexes are updated? I have a daily Solr optimize, and Solr
autocommit enabled.
I have an hourly "doveadm index -A *" command - is that unneeded?
--
Daniel
On 4/12/2015 6:53 AM, Timo Sirainen wrote:
> On 10 Apr 2015, at 21:55,