[
https://issues.apache.org/jira/browse/SOLR-10822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16964151#comment-16964151
]
David Smiley commented on SOLR-10822:
-------------------------------------
How does a shared Policy.Session prevent concurrent collection creations from
placing their replicas on the same nodes? (assuming the default policy:
minimize core count)
A Session appears to be shared & mutable yet I don't see concurrency controls
(e.g. synchronized) to prevent races.
> Concurrent execution of Policy computations should yield correct result
> ------------------------------------------------------------------------
>
> Key: SOLR-10822
> URL: https://issues.apache.org/jira/browse/SOLR-10822
> Project: Solr
> Issue Type: Sub-task
> Components: SolrCloud
> Reporter: Shalin Shekhar Mangar
> Assignee: Noble Paul
> Priority: Major
> Labels: autoscaling
> Fix For: 7.1, 8.0
>
> Attachments: SOLR-10822.patch
>
>
> Policy framework are now used to find replica placements by all collection
> APIs but since these APIs can be executed concurrently, we can get wrong
> placements because of concurrently running calculations. We should
> synchronize just the calculation part so that they happen serially.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
