[
https://issues.apache.org/jira/browse/SOLR-14613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17187004#comment-17187004
]
Ilan Ginzburg commented on SOLR-14613:
--------------------------------------
??Why can't "existing placement strategies" also be a "plugin" (even if it
available as default). Why any distinction between default and custom placement
strategies???
I believe it should be totally possible to implement plugins based on the new
framework, one doing placement like {{LEGACY}} does and the other one like
{{RULES}}. If it's not possible, the plugin framework should be extended to
make it possible (currently there's no support in the plugin framework to
retrieve {{List<Map>}} collection properties needed to access configured rules,
but this is easy to add).
Note that {{RULES}} based implementation is directly accessing internal Solr
classes (i.e. it is not isolated from existing implementation like the
placement plugins are), so porting {{RULES}} to plugins will involve some
rewrite of code interacting with internal abstractions.
If anybody want to do that, now it a perfect time while the placement plugin
implementation is still under discussion and development. I would be happy to
help!
> 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: 20h 40m
> 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
