You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Shalin Shekhar Mangar (JIRA)" <ji...@apache.org> on 2018/07/17 06:44:00 UTC
[jira] [Commented] (SOLR-11990) Make it possible to co-locate
replicas of multiple collections together in a node using policy
[ https://issues.apache.org/jira/browse/SOLR-11990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16546097#comment-16546097 ]
Shalin Shekhar Mangar commented on SOLR-11990:
----------------------------------------------
This patch:
# Changes the approach to use a new ConditionType called WITH_COLLECTION that ensures that we project add replica correctly i.e. during computation, adding a replica for the main collection also adds a replica for the with collection so that we don't generate bad suggestions at all
# SolrClientNodeStateProvider is aware of the `withCollection` flag and returns them in the state
# Move replica, delete collection APIs are aware of with collection
# New integration tests in TestWithCollection.testNodeAdded
# Still a few nocommits left
> Make it possible to co-locate replicas of multiple collections together in a node using policy
> ----------------------------------------------------------------------------------------------
>
> Key: SOLR-11990
> URL: https://issues.apache.org/jira/browse/SOLR-11990
> Project: Solr
> Issue Type: New Feature
> Security Level: Public(Default Security Level. Issues are Public)
> Components: AutoScaling, SolrCloud
> Reporter: Shalin Shekhar Mangar
> Assignee: Shalin Shekhar Mangar
> Priority: Major
> Fix For: master (8.0), 7.5
>
> Attachments: SOLR-11990.patch, SOLR-11990.patch, SOLR-11990.patch, SOLR-11990.patch, SOLR-11990.patch, SOLR-11990.patch
>
>
> It is necessary to co-locate replicas of different collection together in a node when cross-collection joins are performed. The policy rules framework should support this use-case.
> Example: Co-locate exactly 1 replica of collection A in each node where a replica of collection B is present.
> {code}
> {"replica":">0", "collection":"A", "shard":"#EACH", "withCollection":"B"}
> {code}
> This requires changing create collection, create shard and add replica APIs as well because we want a replica of collection A to be created first before a replica of collection B is created so that join queries etc are always possible.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org