[
https://issues.apache.org/jira/browse/SOLR-14275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17044414#comment-17044414
]
Andrzej Bialecki commented on SOLR-14275:
-----------------------------------------
After discussing this with [~noble] here's my attempt at reducing the O(n)
complexity of the calculations. Basically, for each simulated addReplica the
code doesn't test the whole autoscaling matrix for violations, it only tests
the current node (Row).
However, the scenario attached above still runs for > 10 min.
> Policy calculations are very slow for large clusters and large operations
> -------------------------------------------------------------------------
>
> Key: SOLR-14275
> URL: https://issues.apache.org/jira/browse/SOLR-14275
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: AutoScaling
> Affects Versions: 7.7.2, 8.4.1
> Reporter: Andrzej Bialecki
> Assignee: Andrzej Bialecki
> Priority: Major
> Attachments: SOLR-14275.patch, scenario.txt
>
>
> Replica placement calculations performed during collection creation take
> extremely long time (several minutes) when using a large cluster and creating
> a large collection (eg. 1000 nodes, 500 shards, 4 replicas).
> Profiling shows that most of the time is spent in
> {{Row.computeCacheIfAbsent}}, which probably doesn't reuse this cache as much
> as it should.
--
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
