[
https://issues.apache.org/jira/browse/SOLR-11990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16598200#comment-16598200
]
ASF subversion and git services commented on SOLR-11990:
--------------------------------------------------------
Commit 5670d612e3f2512d85c972b5fc717586118a19d5 in lucene-solr's branch
refs/heads/master from [~shalinmangar]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=5670d61 ]
SOLR-11990: When a Collection CREATE command fails because of a policy rule
violation, the collection metadata remains in ZooKeeper, even though no
replicas are added, so the user has to manually delete the zombie collection.
This is due to a change in behavior made in this issue where collection
metadata creation was moved before attempting to use policy to place replicas.
This change reverts the behavior by explicitly deleting the metadata when an
AssignmentException occurs. Since the policy depends on collection metadata
such as WITH_COLLECTION and COLOCATED_WITH properties, moving metadata creation
after policy use would have resulted in passing these properties through the
entire call stack quite invasively. Therefore the current approach is adopted.
> Make it possible to co-locate replicas of multiple collections together in a
> node
> ---------------------------------------------------------------------------------
>
> 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-TestWithCollection-testDeleteWithCollection-fixes.patch,
> SOLR-11990-fix.patch, SOLR-11990.patch, 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.
> while creating a collection specify the parameter
> {{withCollection=other-collection-name}} . This ensure that Solr always
> ensure that atleast one replica of {{other-collection}} is present with this
> collection replicas
> 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.
> Some caveats to this implementation:
> # The {{other-collection}} should only have a single shard named "shard1"
> # Any replica of {{other-collection}} created by this feature will be of NRT
> type
> Removing the above caveats can be a goal of other issues.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
