[
https://issues.apache.org/jira/browse/SOLR-11990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16583604#comment-16583604
]
Shalin Shekhar Mangar commented on SOLR-11990:
----------------------------------------------
The {{TestWithCollection.testDeleteWithCollection}} fails because after
collection is created, we try to delete the linked collection immediately and
sometimes the delete request races with 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 the delete request
succeeds even though it should fail because a linked collection exists.
The attached
{{SOLR-11990-TestWithCollection-testDeleteWithCollection-fixes.patch}} adds a
waitForState command to the CreateCollectionCmd so that the latest state is
visible to the overseer. I also added more asserts so that a successful
deletion should fail the test.
> 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]
