[ 
https://issues.apache.org/jira/browse/SOLR-11990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16597416#comment-16597416
 ] 

Shalin Shekhar Mangar commented on SOLR-11990:
----------------------------------------------

Simple {{SOLR-11990-fix.patch}} to fix the regression. I'll commit this once 
precommit and tests pass. I've fixed this because it is a change in behavior 
from before but the bug is bigger than this fix alone. Any exception after the 
collection is created in ZK can cause the same problem. I'll open a separate 
issue to fix the full problem.

> 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]

Reply via email to