I found how the issue is created .when solr warm up the new searcher with
cacheLists , if the queryResultCache is enable the issue is created.
notice:as I mentioned before I commit with waitflush=false and
waitsearcher=false
so it has problem in case the queryResultCache is on,
but I don't know why the issue is created only in deleteById mode and we
don't have problem when we add a doc and commit with waitflush=false and
waitsearcher=false
I think they both use the same method for warmup the new searcher !!!
there is also a comment on solrCore class that I am concern about it:
solrCore.java
public RefCounted<SolrIndexSearcher> getSearcher(boolean forceNew, boolean
returnSearcher, final Future[] waitSearcher) throws IOException {
------------------
----------------
----------------
line 1132 (nightly version)
// warm the new searcher based on the current searcher.
// should this go before the other event handlers or after?
if (currSearcher != null) {
future = searcherExecutor.submit(
new Callable() {
public Object call() throws Exception {
try {
newSearcher.warm(currSearcher);
} catch (Throwable e) {
SolrException.logOnce(log,null,e);
}
return null;
}
}
);
}
-----
------
}
--
View this message in context:
http://www.nabble.com/solrj-delete-by-Id-problem-tp21433056p21687431.html
Sent from the Solr - User mailing list archive at Nabble.com.
