About once a day a Solr/Jetty process gets hung on my server consuming 100% of
one of the CPU's. Once this happens the server no longer responds to requests.
I've looked through the logs to try and see if anything stands out but so far
I've found nothing out of the ordinary.
My current remedy
2011, at 12:06 PM, Bill Au wrote:
> Taking a thread dump will take you what's going.
>
> Bill
>
> On Wed, Jun 1, 2011 at 3:04 PM, Chris Cowan
> wrote:
>
>> About once a day a Solr/Jetty process gets hung on my server consuming 100%
>> of one of the CPU&
Sorry ... I just found it. I will try that next time. I have a feeling it wont
work since the server usually stops accepting connections.
Chris
On Jun 1, 2011, at 12:12 PM, Chris Cowan wrote:
> I'm pretty green... is that something I can do while the event is happening
>
he machine is multi-core, making
> sure GC happens in a seperate thread is helpful.
>
> But figuring out exactly what's going on requires confusing JVM
> debugging of which I am no expert at either.
>
> On 6/1/2011 3:04 PM, Chris Cowan wrote:
>> About once a day a So
How long does the query against the DB take (outside of Solr)? If that's slow
then it's going to take a while to update the index. You might need to figure a
way to break things up a bit, maybe use a delta import instead of a full import.
Chris
On Jun 4, 2011, at 6:23 AM, Rohit Gupta wrote:
>
oops...
http://search.lucidimagination.com/search/document/bf43af733e898424/busywait_hang_using_extracting_update_handler_on_trunk
Chris
On Jun 4, 2011, at 2:48 PM, Chris Cowan wrote:
> I found this thread that looks similar to what's happening on my system. I
> think what happe
un 4, 2011, at 2:48 PM, Chris Cowan wrote:
> I found this thread that looks similar to what's happening on my system. I
> think what happens is there are multiple commits happening at once from the
> clients and it's causing the same issue. I'm going to use the commitWithin
