[ 
https://issues.apache.org/jira/browse/SOLR-14613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17171841#comment-17171841
 ] 

Ilan Ginzburg commented on SOLR-14613:
--------------------------------------

I just pushed to the [PR|https://github.com/apache/lucene-solr/pull/1684] what 
I believe is a last commit putting it in a _ready to merge_ state.

Next steps from here are on two different and largely independent directions:
 # Create the Solr side implementations supporting these abstractions and wire 
them into existing Collection API commands code to make them use the plugin 
infrastructure when so configured (configuration will be _legacy_ or _rules_ or 
_placement plugins_).
 # Start writing realistic plugins in support of common placement scenarios.

The work in these two directions might uncover missing pieces and 
inefficiencies in the interfaces defined here that will then be fixed. I 
consider this an initial draft clearly indicating the direction of this work:
 * strong typing (IDE help, meaningful method names, almost no casting in 
plugin code etc),
 * ease of use for plugin developers,
 * efficiency (single round trip to any node, no unnecessary fetching of data 
or building of huge datasets),
 * isolation from internal Solr implementation.

Please let me know of any comments, I'd like to check it in this week so 
implementation can start. Note that this code is in a package of its own 
{{org.apache.solr.cluster.placement}}, totally isolated from the rest of Solr 
codebase (which was clearly one of the goals).

[package-info.java|https://github.com/apache/lucene-solr/pull/1684/files#diff-5eea5ec4c2e9ea7ac6830ebcd70549da]
 can be a starting point for looking at this PR, or 
[PlacementPlugin.java|https://github.com/apache/lucene-solr/pull/1684/files#diff-d5559330475ceca951b0bd9bf139fb35]
 or one of the two 
[examples|https://github.com/apache/lucene-solr/pull/1684/files#diff-2680088d60c4854f0b4ba09cf2b5b9dc].

[~ichattopadhyaya], [~ab], [~noble.paul]
  

 

> 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: 11h
>  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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to