[
https://issues.apache.org/jira/browse/SOLR-11990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16583612#comment-16583612
]
ASF subversion and git services commented on SOLR-11990:
--------------------------------------------------------
Commit 6e21cb3aa9451ae72d450ce2e2bb4216a37a7ac8 in lucene-solr's branch
refs/heads/master from [~shalinmangar]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=6e21cb3 ]
SOLR-11990: Create Collection API now waits for the updated state of the
withCollection to be visible after setting the COLOCATED_WITH value
Sometimes deletion of the withCollection succeeds even though the linked
collection exists, if the delete request is sent immediately after the creation
of the linked collection. This is because of a race between the delete request
and the zookeeper update made by create collection such that the COLOCATED_WITH
property is not visible to the overseer collection processor during the delete
request. Therefore, we now wait until the property is visible before returning
a success to the user. The test also adds more asserts so that a similar race
will fail the test immediately with a proper assert message.
> 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.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]
