You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@solr.apache.org by "David Smiley (Jira)" <ji...@apache.org> on 2021/06/01 21:39:00 UTC
[jira] [Commented] (SOLR-15130) Allow per-collection replica
placement node sets
[ https://issues.apache.org/jira/browse/SOLR-15130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17355343#comment-17355343 ]
David Smiley commented on SOLR-15130:
-------------------------------------
[~ab] I have a strong suspicion that the changes here triggered org.apache.solr.client.solrj.io.stream.StreamDecoratorTest.testParallelPriorityStream to start failing at about 7% of the time when it did not prior. See the [CI trend history|http://fucit.org/solr-jenkins-reports/history-trend-of-recent-failures.html#series/org.apache.solr.client.solrj.io.stream.StreamDecoratorTest.testParallelPriorityStream] available at Fucit.org, and notice it started on March 1st.
> 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: main (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: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org