[
https://issues.apache.org/jira/browse/SOLR-10822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16093886#comment-16093886
]
Noble Paul commented on SOLR-10822:
-----------------------------------
Share a Policy.Session object across all the commands
* When a Policy.Session is required, try to borrow one
* if there is no session in use create one create one
* The session will be kept active as long as the suggestions from that session
are being executed. After all the suggestions are executed (or failed), the
session can be destroyed
* If another command needs to do replica placement, and an active session is
available, reuse it
* If no suggestions from a session are being executed, discard the session
> 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
> Security Level: Public(Default Security Level. Issues are Public)
> Components: SolrCloud
> Reporter: Shalin Shekhar Mangar
> Assignee: Noble Paul
> Labels: autoscaling
> Fix For: 7.0
>
>
> 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
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
