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 Solr stops responding, there are no
messages in the logs, nothing. Requests just time
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't seem to
be hitting this issue
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 the same, version of
java is
the same, etc.
We don't have a stack trace and no JMX
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
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't seem
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. Requests just time out.
We have
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't seem to
be hitting this issue. All
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 the same, version of java
is
the same, etc.
We don't have a stack
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 Solr stops responding, there are no
messages in the logs, nothing. Requests just time out.
We have also only seen
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 the same, version of java is
the same
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
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?
Sorry for bunch of short self-replies, just trying to analyse...
CPU may get overloaded by constantly running GC trying to
defragmentoptimize 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
13 matches
Mail list logo
