Hmmm, thanks. This line:
org.apache.solr.update.DefaultSolrCoreState.newIndexWriter(org.apache.solr.core.SolrCore,
boolean) @bci=89, line=157 (Interpreted frame)
is suspiciously in the region of SOLR-7836 but the rest of the
precursors for that JIRA aren't
present (i.e. Delete By Query and/or rel
Sure, Eric. Here it is
Attaching to process ID 9429, please wait...
Debugger attached successfully.
Server compiler detected.
JVM version is 25.51-b03
Deadlock Detection:
No deadlocks found.
Thread 9578: (state = BLOCKED)
- sun.misc.Unsafe.park(boolean, long) @bci=0 (Compiled frame; informatio
Hmm, it would be _really_ helpful if next time it happens you could
get a stack trace (see jstack, should have come with your Java). As it
happens we're chasing another deadlock and it'd be interesting to see
if they're related.
Thanks!
Erick
On Tue, Aug 11, 2015 at 1:12 AM, Andrii Berezhynskyi
Hi,
I have solr5.2.1 set up in master-slave configuration. Very often it
happens that solr slave starts replicating (I can see it in admin panel)
but it is getting stuck at 0% and never proceeds further. Usually restart
of slave helps.
Relevant logs from slave:
INFO - 2015-08-11 07:56:00.184; o
