Run jstack on the solr process (standard with Java) and look for the word "semaphore". You should see your servers blocked on this in the Solr code. That'll pretty much nail it.
There's an open JIRA to fix the underlying cause, see: SOLR-5232, but that's currently slated for 4.6 which won't be cut for a while. Also, there's a patch that will fix this as a side effect, assuming you're using SolrJ, see. This is available in 4.5 SOLR-4816 Best, Erick On Tue, Oct 15, 2013 at 1:33 PM, michael.boom <my_sky...@yahoo.com> wrote: > Here's some of the Solr's last words (log content before it stoped > accepting > updates), maybe someone can help me interpret that. > http://pastebin.com/mv7fH62H > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Concurent-indexing-tp4095409p4095642.html > Sent from the Solr - User mailing list archive at Nabble.com. >
