Hello,
I read that it's being worked on 6x to fix the limitation of CDCR only covering
the active-passive scenario. My question is then - does anyone know when we can
expect the fix to be out?
Thanks,
Mads
OSE_WAIT issue at a customer. I am running
> > some tests with different versions trying to pinpoint the cause of this
> > leak.
> > Once I have some more information and a reproducible test, I'll open
> > a
> jira
> > issue. I'll keep you post
Hello there,
Our SolrCloud is experiencing a FD leak while running with SSL. This is
occurring on the one machine that our program is sending data too. We have a
total of three servers running as an ensemble.
While running without SSL does the FD Count remain quite constant at around 180
while
Another update:
After creating a new certificate, properly specified for its use of context, do
we still end up in the described situation. Thus, it seems SSL itself is the
underlying reason for the leak -
-Original Message-
From: Mads Tomasgård Bjørgan [mailto:m...@dips.no]
Sent
SolrCloud with the same certificate.
Thanks,
Mads
From: Mads Tomasgård Bjørgan [mailto:m...@dips.no]
Sent: tirsdag 5. juli 2016 09.46
To: solr-user@lucene.apache.org
Subject: Memory issues when indexing
Hello,
We're struggling with memory-issues when posting documents to Solr - and unsure
Hello,
We're struggling with memory-issues when posting documents to Solr - and unsure
for which reason the problem occurs.
The documents are indexed in a SolrCloud running Solr 6.1.0 on top of Zookeeper
3.4.8, utilizing three VMs running CentOS 7 and JRE 1.8.0.
After various attempts with
That's true, but I was hoping there would be another way to solve this issue as
it's not considered preferable in our situation.
Is it normal behavior for Solr to open over 4000 files without closing them
properly? Is it for example possible to adjust autoCommit-settings I
solrconfig.xml for
Hello,
We're indexing a large set of files using Solr 6.1.0, running a SolrCloud by
utilizing ZooKeeper 3.4.8.
We have two ensembles - and both clusters are running on three of their own
respective VMs (CentOS 7). We first thought the error was due to CDCR - as we
were trying to index a large
