Hmmm, why all those tomcats? Are they all running Solr?
I'm pretty sure you'd be a lot better off simply having
one indexer and one searcher on this box. Give the searcher
the most resources I'd guess. In fact, you'd
be even better off offloading the indexing process to a different
(perhaps less po
Excuse me, I mean an Apache Tomcat 6.
Hello, Erik.
Thank you for answering again. I'm using Java JDK 1.5 and an Apache Tomcat
1.6 configuring it's memory parameters from 1G to 2G maximum for each Tomcat
server. The machine has a RAID5 HDD, 32G RAM and eight cores, and I have six
Tomcat launched with their process running at the same t
Well, if the documents do get indexed, then all you have to do
is lengthen the timeout for your connection, what is it set at now?
But this isn't expected. The first place I'd look is whether your
indexing machine is allowing the op system enough memory
to manage its disk caches well. The second q
Hello, Erik.
Thank you for answering. The performance decreases during indexing: while
replication is in process the batch machine could not recieve and process
quickly the indexing petitions and some "read timed out" exceptions appear.
Luckily I just load some hundreds of documents every day beca
Luis:
First, I managed to "invite you to chat" by mistake, don't se a way to
cancel it... Sorry.
Anyway, what exactly slows down? Indexing? search performance on the slaves?
We need some more details to answer your questions, it might help to review:
http://wiki.apache.org/solr/UsingMailingL
Hello.
I have the suspicion that while the replication is in process from a batch
machine to N slaves machines I have performance problems: read timed out
exceptions, etc. The thing is that I have deployed a real time environment
where the batch machine recieves petitions, process them and then in
