[
https://issues.apache.org/jira/browse/SOLR-4055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13495016#comment-13495016
]
Commit Tag Bot commented on SOLR-4055:
--------------------------------------
[branch_4x commit] Mark Robert Miller
http://svn.apache.org/viewvc?view=revision&revision=1408126
SOLR-4055: Fix a thread safety issue with the Collections API that could cause
actions to be targeted at the wrong SolrCores.
> Remove/Reload the collection has the thread safe issue.
> -------------------------------------------------------
>
> Key: SOLR-4055
> URL: https://issues.apache.org/jira/browse/SOLR-4055
> Project: Solr
> Issue Type: Bug
> Components: SolrCloud
> Affects Versions: 4.0-ALPHA, 4.0-BETA, 4.0
> Environment: Solr cloud
> Reporter: Raintung Li
> Assignee: Mark Miller
> Fix For: 4.1, 5.0
>
> Attachments: patch-4055
>
>
> OverseerCollectionProcessor class for collectionCmd method has thread safe
> issue.
> The major issue is ModifiableSolrParams params instance will deliver into
> other thread use(HttpShardHandler.submit). Modify parameter will affect the
> other threads the correct parameter.
> In the method collectionCmd , change the value
> params.set(CoreAdminParams.CORE, node.getStr(ZkStateReader.CORE_NAME_PROP));
> , that occur send the http request thread will get the wrong core name. The
> result is that can't delete/reload the right core.
> The easy fix is clone the ModifiableSolrParams for every request.
--
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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
