The first question is "what's been changing"? I suspect something's been
growing
right along and finally tripped you up. Places I would look first:
1> how much free space is on your disk? Have your logs (or other files)
grown without bound?
2> If this is a Unix box, what does "top" report? In other words, profile
your machine and
see what the limiting resources is. You should be seeing something
pathalogical.
Your CPUs should be pegged (find out the program using it up). Or your
I/O is swapping
like a crazy thing. Or....
Until you have some clue where you're being starved, you're just guessing...
Even negative
data is better than none (i.e. being CPU bound rules out most I/O problems
and vice-versa).
It's even possible that what's happening is that some other program on that
box is
mis-behaving and starving your searcher process. The possibilities are
endless.
A *very* quick way to test a lot would be to move the searcher onto another
box and see
what happens then.
Best
Erick
On Mon, Oct 11, 2010 at 2:36 PM, Hitendra Molleti
<hitendra.moll...@itp.com>wrote:
> Hi,
>
>
>
> We are running a CMS based on Java and use Solr 1.4 as the indexer.
>
>
>
> Till today afternoon things were fine until we hit this Solr issue where it
> sort of becomes unresponsive. We tried to stop and restart Solr but no
> help.
>
>
>
> When we look into the logs Solr is receiving queries and running them but
> we
> do not seem to get the responses and after an endless wait the page
> generates a 503 error (Varnish on the front end).
>
>
>
> Can someone help us with any possible suggestions or solutions.
>
>
>
> Thanks
>
>
>
> Hitendra
>
>
