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

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

My plan in the PR I will share is to define the interfaces and provide sample 
plugins implementations showing simple yes somewhat useful placement 
implementations. For example random but no 2 replicas of same shard on same 
node or something that spreads replicas based on some system property (for 
Availability zone approach), or just the current default equal number of cores 
per node, highest minimal amount of remaining free disk space.

+I do not plan+ to propose implementations for the interfaces at this stage 
(although obviously I'm keeping this need in the back of my mind to propose 
realistic interfaces) so we can agree on *what* before we enter the discussion 
of *how*...

> Provide a clean API for pluggable autoscaling implementations
> -------------------------------------------------------------
>
>                 Key: SOLR-14613
>                 URL: https://issues.apache.org/jira/browse/SOLR-14613
>             Project: Solr
>          Issue Type: Improvement
>          Components: AutoScaling
>            Reporter: Andrzej Bialecki
>            Priority: Major
>          Time Spent: 5h 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

Reply via email to