in context:
> http://lucene.472066.n3.nabble.com/solr-tomcat-stops-responding-tp474577p3998435.html
> Sent from the Solr - User mailing list archive at Nabble.com.
>
Developer
--
View this message in context:
http://lucene.472066.n3.nabble.com/solr-tomcat-stops-responding-tp474577p3998435.html
Sent from the Solr - User mailing list archive at Nabble.com.
OK, this may fix it:
https://issues.apache.org/jira/browse/SOLR-77
A war with this patch included is here:
http://people.apache.org/~yonik/solr/current/solr.war
You also need to configure some queries to be done on the firstSearcher event
in solrconfig.xml. Uncomment and customize the example o
On 12/3/06, Kevin Lewandowski <[EMAIL PROTECTED]> wrote:
Okay, I figured out how to get the thread dump. It was in the tomcat
logfile. I'm attaching it here.
Nothing sticks out to me as problematic, except for the 150 concurrent
requests in progress!
Perhaps the real problem already passed, and
On 12/2/06, Kevin Lewandowski <[EMAIL PROTECTED]> wrote:
I've done a temporary fix for this by running a proxy in front of
tomcat. Then I updated my system startup to start solr, wait 20
seconds, run a few queries, wait 20 seconds, then start the proxy.
This is working fine now. But I'd still lik
Hmmm, on most Linux/UNIX systems, sending the QUIT signal does nothing
else but generate a stack trace to the console or a log file. If you
don't start tomcat by hand, the stack trace may go somewhere else I
suppose. This would be useful to learn how to do on your particular
system (and we shoul
On 12/2/06, Kevin Lewandowski <[EMAIL PROTECTED]> wrote:
> accept connections for 3 or 4 hours ... did you try taking some thread
> dumps like yonik suggested to see what all the threads were doing?
A kill -3 will not kill the process. It does nothing and there's no
thread dump on the console. k
accept connections for 3 or 4 hours ... did you try taking some thread
dumps like yonik suggested to see what all the threads were doing?
A kill -3 will not kill the process. It does nothing and there's no
thread dump on the console. kill -9 does kill it though.
btw, this has been a bigger prob
: Okay, I did that. Shut off traffic to the server, restarted solr, ran
: a few queries against it, then turned traffic back on, and it's
: running fine now. So maybe the initial flood of requests has something
: to do with it?
an initial flood of requests to a completley cold index can definitel
> My solr installation has been running fine for a few weeks but now
> after a server reboot it starts and runs for a few seconds, then stops
> responding. I don't see any errors in the logfiles, apart from
> snapinstaller not being able to issue a commit. Also, the process is
> using 100% cpu and
On 12/1/06, Kevin Lewandowski <[EMAIL PROTECTED]> wrote:
My solr installation has been running fine for a few weeks but now
after a server reboot it starts and runs for a few seconds, then stops
responding. I don't see any errors in the logfiles, apart from
snapinstaller not being able to issue a
My solr installation has been running fine for a few weeks but now
after a server reboot it starts and runs for a few seconds, then stops
responding. I don't see any errors in the logfiles, apart from
snapinstaller not being able to issue a commit. Also, the process is
using 100% cpu and stops res
12 matches
Mail list logo
