[
https://issues.apache.org/jira/browse/SOLR-3861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13462449#comment-13462449
]
Yandong Yao commented on SOLR-3861:
-----------------------------------
@Hoss,
Comment related with SOLR-2008 and this:
We are using many shards, and will load/unload shards according to its usage
pattern. Sometime when we try to unload shards, we encounter issues mentioned
in SOLR-2008.
I am not sure whether this will result in any data loss, (we have encountered
some issues, while it is caused by our client code mostly, we have used read
write lock to protect unloading shard code, so that if there are threads
indexing data to this shard, then it won't be unloaded. After this change, so
far so good. while we still encounter exception mentioned in SOLR-2008 in solr
log).
Also we have encountered following exception sometimes when we try to unloading
shard (we will always call commit before unloading shard):
BTW: we are using one old (lucene.version=4.0-SNAPSHOT 1189391) solr 4 snapshot
build.
Sep 14, 2012 4:49:22 AM org.apache.solr.common.SolrException log
SEVERE: auto commit error...:java.lang.RuntimeException:
org.apache.lucene.util.ThreadInterruptedException:
java.lang.InterruptedException: sleep interrupted
at org.apache.solr.core.SolrCore.getSearcher(SolrCore.java:1140)
at org.apache.solr.core.SolrCore.getSearcher(SolrCore.java:999)
at
org.apache.solr.update.DirectUpdateHandler2.commit(DirectUpdateHandler2.java:339)
at org.apache.solr.update.CommitTracker.run(CommitTracker.java:184)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:98)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:206)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Caused by: org.apache.lucene.util.ThreadInterruptedException:
java.lang.InterruptedException: sleep interrupted
at
org.apache.lucene.index.SegmentInfos$FindSegmentsFile.run(SegmentInfos.java:644)
at org.apache.lucene.index.DirectoryReader.open(DirectoryReader.java:84)
at org.apache.lucene.index.IndexReader.open(IndexReader.java:536)
at org.apache.lucene.index.IndexReader.open(IndexReader.java:495)
at
org.apache.solr.core.StandardIndexReaderFactory.newReader(StandardIndexReaderFactory.java:38)
at
org.apache.solr.search.SolrIndexSearcher.<init>(SolrIndexSearcher.java:109)
at org.apache.solr.core.SolrCore.getSearcher(SolrCore.java:1130)
... 11 more
Caused by: java.lang.InterruptedException: sleep interrupted
at java.lang.Thread.sleep(Native Method)
at
org.apache.lucene.index.SegmentInfos$FindSegmentsFile.run(SegmentInfos.java:642)
... 17 more
> regresion of SOLR-2008 - updateHandler should be closed before
> searcherExecutor
> -------------------------------------------------------------------------------
>
> Key: SOLR-3861
> URL: https://issues.apache.org/jira/browse/SOLR-3861
> Project: Solr
> Issue Type: Bug
> Affects Versions: 4.0-ALPHA, 4.0-BETA
> Reporter: Hoss Man
> Assignee: Mark Miller
> Priority: Blocker
> Fix For: 4.1, 5.0
>
> Attachments: SOLR-3861.patch
>
>
> SOLR-2008 fixed a possible RejectedExecutionException by ensuring that
> SolrCore closed the updateHandler before the searcherExecutor.
> [[email protected]] re-flipped this logic in r1159378, which is
> annotated as fixing both SOLR-2654 and SOLR-2654 (dup typo i guess) but it's
> not clear why - pretty sure this means that the risk of a Rejected exception
> is back in 4.0-BETA...
> https://svn.apache.org/viewvc/lucene/dev/trunk/solr/core/src/java/org/apache/solr/core/SolrCore.java?r1=1146905&r2=1159378
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
