Try to use Tomcat... I never had SOLR-deadlocks (I believe) on 4-CPU
SLES 10 server; only OutOfMemoryExceptions (possibly due to faceting,
and significant memory fragmentation)
Recent OOM happened because I run MySQL on same server, and I overloaded it...
OpenBitSet & Faceting is main memory
e doesn't seem to be any reason for it from what we
can
tell. We haven't seen it in QA or development.
We're running Solr with basically the example Solr setup with
Jetty
(6.1.3). We package our Solr install by using 'ant example' and
replacing configs/etc. Whenever So
w issues with Solr not responding to requests (searches or admin
pages). There doesn't seem to be any reason for it from what we can
tell. We haven't seen it in QA or development.
We're running Solr with basically the example Solr setup with Jetty
(6.1.3). We package our Solr install
few weeks ago, we've seen a
few issues with Solr not responding to requests (searches or admin
pages). There doesn't seem to be any reason for it from what we can
tell. We haven't seen it in QA or development.
We're running Solr with basically the example Solr setup with Je
Sorry for bunch of short self-replies, just trying to analyse...
CPU may get overloaded by constantly running GC trying to
defragment&optimize memory, in a loop (constant queue of requests);
response time will be few minutes (in best cases) and contain 500...
so that sometimes we can't see
Just as a sample, SolrCore contains blocks like
} catch (Throwable e) {
SolrException.logOnce(log,null,e);
}
And SolrServlet:
} catch (Throwable e) {
SolrException.log(log,e);
sendErr(500, SolrException.toStr(e), request, response);
}
What will happen with OutOfMemoryError? I
I suspect that SolrException is used to catch ALL exceptions in order
to show "500 OutOfMemory" in HTML/XML/JSON etc., so that JVM simply
hangs... weird HTTP understanding...
Quoting Fuad Efendi <[EMAIL PROTECTED]>:
Following lines are strange, looks like SOLR deals with OOM and
rethrows
id=0x401356e0
nid=0x5d88 runnable
"VM Periodic Task Thread" prio=1 tid=0x40129ab0 nid=0x5d91
waiting on condition
==
http://www.linkedin.com/in/liferay
Quoting Noble Paul ??? ?? <[EMAIL PROTECTED]>:
Can we collect more inform
admin
>> pages). There doesn't seem to be any reason for it from what we can
>> tell. We haven't seen it in QA or development.
>>
>> We're running Solr with basically the example Solr setup with Jetty
>> (6.1.3). We package our Solr install by using &#
r install by using 'ant example' and
replacing configs/etc. Whenever Solr stops responding, there are no
messages in the logs, nothing. Requests just time out.
We have also only seen this on our slaves. The master doesn't seem
to
be hitting this issue. All the boxes are th
lly the example Solr setup with Jetty
(6.1.3). We package our Solr install by using 'ant example' and
replacing configs/etc. Whenever Solr stops responding, there are no
messages in the logs, nothing. Requests just time out.
We have also only seen this on our slaves. The master doesn&
Doug Steigerwald pisze:
> We're running Solr with basically the example Solr setup with Jetty
> (6.1.3). We package our Solr install by using 'ant example' and
> replacing configs/etc. Whenever Solr stops responding, there are no
> messages in the logs, nothing. Requ
r with basically the example Solr setup with Jetty
(6.1.3). We package our Solr install by using 'ant example' and
replacing configs/etc. Whenever Solr stops responding, there are no
messages in the logs, nothing. Requests just time out.
We have also only seen this on our slave
13 matches
Mail list logo
