Glad you found a solution!
Best,
Erick
On Tue, Dec 2, 2014 at 4:30 AM, Doss wrote:
> Dear Erick,
>
> Thanks for your thoughts, it helped me a lot. In my instances no solr logs
> are appended in to catalina.out.
>
> Now I placed the log4j.properties file. Solr logs are captured in solr.log
> file
Dear Erick,
Thanks for your thoughts, it helped me a lot. In my instances no solr logs
are appended in to catalina.out.
Now I placed the log4j.properties file. Solr logs are captured in solr.log
file with the help of it I found the reason for the issue.
I am starting tomcat with the option -Dboo
Doss:
Tomcat often puts things in "catalina.out", you might check there,
I've often seen logging information from Solr go there by
default.
Without having some idea what kinds of problems Solr is
reporting when you see this situation, it's really hard to say.
Some things I'd check first though,
Dear Erick,
Forgive my ignorance.
Please find some of the details you required.
*have you looked at the solr logs?*
> Sorry I haven't defined the log4j.properties file, so I don't have solr
logs. Since it requires tomcat restart I am planning to do it in next
restart.
But found the following
You've really got to provide details for us to say much
of anything. There are about a zillion things that it could be.
In particular, have you looked at the solr logs? Are there
any interesting things in them? How big are the cores?
How much memory are you allocating the JVM? How
many docs in the
I have two node SOLR (4.9.0) cloud with Tomcat (8), Zookeeper. At times
SOLR in Node 1 stops responding, to fix the issue I am restarting tomcat in
Node 1, but SOLR not starting up, but if I remove the solr cores in both
nodes and try restarting it starts working, and then I have to reindex the
who
