[ 
https://issues.apache.org/jira/browse/SOLR-3861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13463480#comment-13463480
 ] 

Yandong Yao commented on SOLR-3861:
-----------------------------------

Hi Mark,

do you mean this issue (RejectException) won't impact system such as lost 
uncommitted documents? 

It seems happen when autocommit code try to run while the core is closing, 
could we run commit before close and then disable autocommit in core closing 
code.

How about above 'sleep interrupted' exception? Are they caused by same reason?

Thanks,
Yandong
                
> 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-3861.patch, 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]

Reply via email to