[
https://issues.apache.org/jira/browse/SOLR-915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12656535#action_12656535
]
Shalin Shekhar Mangar commented on SOLR-915:
--------------------------------------------
Kay, I guess all we are trying to avoid is the [XY
problem|http://people.apache.org/~hossman/#xyproblem].
We just want to make sure that we are solving the right problem. Do you mind
telling us about your use-case on solr-user because the solution you have
adopted is not something the code was written for. Perhaps there are alternate
ways of achieving the goals? There are lots of people on these lists who have
done some very heavy lifting with Solr and might be able to offer suggestions.
> SolrCore;close() - scope to exploit parallelism among the number of
> closeHooks
> --------------------------------------------------------------------------------
>
> Key: SOLR-915
> URL: https://issues.apache.org/jira/browse/SOLR-915
> Project: Solr
> Issue Type: Improvement
> Environment: Tomcat 6, JRE 6
> Reporter: Kay Kay
> Original Estimate: 96h
> Remaining Estimate: 96h
>
> In SolrCore: close() - all the way towards the end of the function - there
> seems to be a sequential list of close method invocation.
> if( closeHooks != null ) {
> for( CloseHook hook : closeHooks ) {
> hook.close( this );
> }
> }
> I believe this has scope to be parallelized ( actually the entire sequence of
> close operations , updateHandler,close() etc.) - by means of launching them
> in separate threads from an ExecutorService , for a much faster shutdown as
> the process definitely does not need to be sequential.
> This becomes all the more important in the multi-core context when we might
> want to shutdown and restart a SolrCore altogether.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
