Hi Martin;
You can change your Java version from 1.6 to 1.7 u25 and test it again to
see that whether it is related to version of Java.
Thanks;
Furkan KAMACI
2013/11/24 Lance Norskog
> Yes, you should use a recent Java 7. Java 6 is end-of-life and no longer
> supported by Oracle. Also, read u
Yes, you should use a recent Java 7. Java 6 is end-of-life and no longer
supported by Oracle. Also, read up on the various garbage collectors. It
is a complex topic and there are many guides online.
In particular there is a problem in some Java 6 releases that causes a
massive memory leak in S
We did some more monitoring and have some new information:
Before
the issue happens the garbage collector's "collection count" increases a
lot. The increase seems to start about an hour before the real problem
occurs:
http://www.analyticsforapplications.com/GC.png [1]
We tried
both the g1
://lucene.472066.n3.nabble.com/SolrCloud-unstable-tp4100419p4100432.html
Sent from the Solr - User mailing list archive at Nabble.com.
Hello,
I’m experiencing sort of the same issue, but with much smaller indexes -
although with much higher latency on disks during backup sessions on our NFS. I
have a feeling the solution could be the same, so I’ll just leave my story here
just in case, no solution found yet.
http://lucene.472
Hi Martin,
I have the same behaviour that you are describing with a setup that is pretty
equal.
6 machines, ~50 shards with replicationFactor equal two.
The most critical issue IMHO is the fact of the failover doens't work because a
node is down and the other in recovery mode.
In log I can se
Hi,
We have:
Solr 4.5.1 - 5 servers
36 cores, 2 shards each, 2 servers per shard (every core is on 4
servers)
about 4.5 GB total data on disk per server
4GB JVM-Memory per server, 3GB average in use
Zookeeper 3.3.5 - 3 servers (one shared with Solr)
haproxy load balancing
Our Solrcloud is ver
