no core reloading. But this is a non-standard core/schema loading
process.
Reverting to an older copy of solr/lucene makes this go away (at least
not show up)
any thoughts where to look? I have not looked too deeply.
ryan
On Feb 25, 2009, at 11:47 PM, Yonik Seeley wrote:
Hmmm, I don't believe Solr calls interrupt anywhere itself...
Would shutting down the executor cause that? Are you doing any core
reloading?
-Yonik
http://www.lucidimagination.com
On Wed, Feb 25, 2009 at 6:01 PM, Ryan McKinley <ryan...@gmail.com>
wrote:
I just upgraded to /trunk from a nightly a few weeks ago. I am now
seeing
an error I did not see before:
2009-02-25 02:50:48,756 ERROR org.apache.solr.update.UpdateHandler -
java.lang.InterruptedException
at
java
.util
.concurrent
.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(Unknown
Source)
at java.util.concurrent.FutureTask$Sync.innerGet(Unknown
Source)
at java.util.concurrent.FutureTask.get(Unknown Source)
at
org
.apache
.solr.update.DirectUpdateHandler2.commit(DirectUpdateHandler2.java:
404)
at
org
.apache
.solr
.update
.processor
.RunUpdateProcessor.processCommit(RunUpdateProcessorFactory.java:78)
at
org
.apache
.solr
.handler.RequestHandlerUtils.handleCommit(RequestHandlerUtils.java:
105)
at
org
.apache
.solr
.handler
.ContentStreamHandlerBase
.handleRequestBody(ContentStreamHandlerBase.java:48)
at
org
.apache
.solr
.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:
131)
at org.apache.solr.core.SolrCore.execute(SolrCore.java:1333)
at
org
.apache
.solr
.client
.solrj.embedded.EmbeddedSolrServer.request(EmbeddedSolrServer.java:
139)
at
org
.apache
.solr.client.solrj.request.UpdateRequest.process(UpdateRequest.java:
243)
at
org.apache.solr.client.solrj.SolrServer.commit(SolrServer.java:85)
at
org.apache.solr.client.solrj.SolrServer.commit(SolrServer.java:74)
...
This points to:
// if we are supposed to wait for the searcher to be registered,
then we
should do it
// outside of the synchronized block so that other update
operations can
proceed.
if (waitSearcher!=null && waitSearcher[0] != null) {
try {
waitSearcher[0].get();
}
any thoughts on what could be going on?
ryan
