[
https://issues.apache.org/jira/browse/SOLR-15130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrzej Bialecki resolved SOLR-15130.
-------------------------------------
Fix Version/s: master (9.0)
Resolution: Fixed
> Allow per-collection replica placement node sets
> ------------------------------------------------
>
> Key: SOLR-15130
> URL: https://issues.apache.org/jira/browse/SOLR-15130
> Project: Solr
> Issue Type: Improvement
> Reporter: Andrzej Bialecki
> Assignee: Andrzej Bialecki
> Priority: Major
> Fix For: master (9.0)
>
> Time Spent: 2h
> Remaining Estimate: 0h
>
> This is an extension of the existing {{replica_type}} concept in the
> {{AffinityPlacementPlugin}}.
> Currently this concept allows users to distribute the placement of new
> replicas by type (NRT, TLOG, PULL) if the target nodes specify the list of
> allowed replica types that they accept. This can be easily extended to
> support any other system property value that the node reports, and pair it
> with any other collection property instead of replica type.
> The motivation for this is the use case where a cluster is logically divided
> into nodes with different types of work load (eg. searching, indexing and
> analytics). Currently it's not possible to configure the placement plugin in
> a way that automatically puts some collections on specific node sets -
> instead users would have to always specify the appropriate node set in every
> CREATE / ADD / MOVE replica request.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
