at 4:49 PM, Jasper Floor wrote:
> Actually, the readOnly=true makes things worse.
> What it does (among other things) is:
> c.setTransactionIsolation(Connection.TRANSACTION_READ_UNCOMMITTED);
>
> which leads to:
> Caused by: org.postgresql.util.PSQLException: Cann
> caused some log warnings, and it wouldn't work at all without readOnly=false.
> Not sure abour PostgreSql.
>
> James Dyer
> E-Commerce Systems
> Ingram Content Group
> (615) 213-4311
>
>
> -Original Message-
> From: Jasper Floor [mailto:jasper.fl..
Hi all,
It seems that DIH always holds two connections open to the database.
One of them is almost always 'idle in transaction'. It may sometimes
seem to do a little work but then it goes idle again.
datasource definition:
We have a datasource defined in the jndi:
Btw, confirmed that this doesn't happen on our development stage with 3.6.
On Wed, May 16, 2012 at 3:59 PM, Jasper Floor wrote:
> The slave index does indeed grow over a period of time regardless of
> restarts. We do run on 1.4 however. We will be updating to 3.6 very
> soon how
g over a longer period of time
>> than just a single replication, is that true?
>>
>> Best
>> Erick
>>
>> On Fri, May 11, 2012 at 6:03 AM, Jasper Floor wrote:
>>> Hi,
>>>
>>> On Thu, May 10, 2012 at 5:59 PM, Otis Gospodnetic
>>
r one, right? If so,
> why is commit needed when you *read* data from DB?
>
> Otis
>
> Performance Monitoring for Solr / ElasticSearch / HBase -
> http://sematext.com/spm
>
>
>
> - Original Message -
>> From: Jasper Floor
>> To: solr
mvg,
Jasper
> You may also want to look at your Index report in SPM
> (http://sematext.com/spm) before/during/after replication and share what you
> see.
>
> Otis
>
> Performance Monitoring for Solr / ElasticSearch / HBase -
> http://sematext.com/spm
>
>
Perhaps I am missing the obvious but our slaves tend to run out of
disk space. The index sizes grow to multiple times the size of the
master. So I just toss all the data and trigger a replication.
However, can't solr handle this for me?
I'm sorry if I've missed a simple setting which does this for
Hi all,
we've been running Solr 1.4 for about a year with no real problems. As
of monday it became impossible to do a full import on our master
because of an OOM. Now what I think is strange is that even after we
more than doubled the available memory there would still always be an
OOM. We seem t
Why not pass the parameters using "?parameter1=value1¶meter2=value2" ?
mvg,
Jasper
On Thu, Apr 26, 2012 at 9:03 PM, Paul Libbrecht wrote:
> Or write your own query component mapping /solr/* in the web.xml, exposing
> the request by a thread-local through a filter, and reading this setting the
10 matches
Mail list logo
