: We have master/slave setup. We disabled autocommits/autosoftcommits. So the
: slave only replicates from master and serve query. Master does all the
: indexing and commit every 5 minutes. Slave polls master every 2.5 minutes
: and does replication.
Details matter...
Are you using hte exact sam
We have master/slave setup. We disabled autocommits/autosoftcommits. So the
slave only replicates from master and serve query. Master does all the
indexing and commit every 5 minutes. Slave polls master every 2.5 minutes
and does replication.
Both tests with Solr 3.5 and 4.2 was run with the same
Here is the JVM info:
$ java -version
java version "1.6.0_26"
Java(TM) SE Runtime Environment (build 1.6.0_26-b03)
Java HotSpot(TM) 64-Bit Server VM (build 20.1-b02, mixed mode)
--
View this message in context:
http://lucene.472066.n3.nabble.com/Solr-4-memory-usage-increase-tp4064066p4064271.h
Yeah how to turn off index writer ?
On Friday, May 17, 2013, Andre Bois-Crettez wrote:
> Can you explain your setup more ?
> ie. is it master/slave, indexing in parallel, etc ?
>
> We had to commit more often to reduce JVM memory usage due to
> transaction logs in SolrCloud mode, compared with pr
Can you explain your setup more ?
ie. is it master/slave, indexing in parallel, etc ?
We had to commit more often to reduce JVM memory usage due to
transaction logs in SolrCloud mode, compared with previous setups
without tlogs.
update?commit=true&openSearcher=false
André
On 05/17/2013 09:56 A
I get the same issue in 1.7.0_09-b05 also.
./zahoor
On 17-May-2013, at 12:07 PM, Walter Underwood wrote:
> It is past time to get off of Java 6. That is dead. End of life. No more
> updates, not even for security bugs.
>
> What version of Java 6? Some earlier versions had bad bugs that Solr
It is past time to get off of Java 6. That is dead. End of life. No more
updates, not even for security bugs.
What version of Java 6? Some earlier versions had bad bugs that Solr would run
into. We hit them in prod until we upgraded.
wunder
On May 16, 2013, at 11:28 PM, Wei Zhao wrote:
> No,
No, exactly the same JVM of Java6
--
View this message in context:
http://lucene.472066.n3.nabble.com/Solr-4-memory-usage-increase-tp4064066p4064108.html
Sent from the Solr - User mailing list archive at Nabble.com.
Did you switch the JVM too?
On Thu, May 16, 2013 at 7:14 PM, Wei Zhao wrote:
> We are migrating from Solr 3.5 to Solr 4.2.
>
> After some performance testing, we found 4.2's memory usage is a lot higher
> than 3.5. Our 12GM max heap process used to handle the test pretty well
> with
> 3.5. whil
