[
https://issues.apache.org/jira/browse/SOLR-14613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17164590#comment-17164590
]
Ilan Ginzburg commented on SOLR-14613:
--------------------------------------
I did a few minor changes in the PR
([https://github.com/apache/lucene-solr/pull/1684]) and heading for a week out
without updates (but can do mail/Slack ;)).
The remaining work is:
# Make sure we are all aligned. There were comments about the verbosity
(number of interfaces), I agree but feel it's necessary to maintain the
isolation from existing Solr Code and have a strongly typed framework.
# Go through all uses of the Autoscaling framework from Collection API
commands and make sure there's support in these interfaces for achieving the
related assignments. Likely means a few additions.
# Decide of a decent home (a.k.a package name) and possible renaming and push
this to master so work can start on the actual implementation (as this PR only
has interfaces!). I believe these interfaces should live in a package
containing no other classes or interfaces.
Not included in this PR (or this Jira for that matter) is work related to
"triggers" (execution based on conditions or scheduling). Let's get assignment
correct first.
I'd like to converge on a common decision within a week (as I don't want to
continue work on this further if work is to then be undone). So let's have
another proposal or two (including porting the sample plugin examples to
compare apples to apples) if anybody feels strongly against the approach here.
Thanks!
> Provide a clean API for pluggable replica assignment implementations
> --------------------------------------------------------------------
>
> Key: SOLR-14613
> URL: https://issues.apache.org/jira/browse/SOLR-14613
> Project: Solr
> Issue Type: Improvement
> Components: AutoScaling
> Reporter: Andrzej Bialecki
> Assignee: Ilan Ginzburg
> Priority: Major
> Time Spent: 8h
> Remaining Estimate: 0h
>
> As described in SIP-8 the current autoscaling Policy implementation has
> several limitations that make it difficult to use for very large clusters and
> very large collections. SIP-8 also mentions the possible migration path by
> providing alternative implementations of the placement strategies that are
> less complex but more efficient in these very large environments.
> We should review the existing APIs that the current autoscaling engine uses
> ({{SolrCloudManager}} , {{AssignStrategy}} , {{Suggester}} and related
> interfaces) to see if they provide a sufficient and minimal API for plugging
> in alternative autoscaling placement strategies, and if necessary refactor
> the existing APIs.
> Since these APIs are internal it should be possible to do this without
> breaking back-compat.
--
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
