Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@lucene.apache.org
Date: Wed, 21 Nov 2012 21:44:57 +0000 (UTC)
From: "Jethro Bakker (JIRA)" <jira@apache.org>
To: dev@lucene.apache.org
Message-ID: <1832272752.14307.1353534297969.JavaMail.jiratomcat@arcas>
Subject: [jira] [Created] (SOLR-4104) SolrCloudServer doesn't support
 multiple collections on same node
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Jethro Bakker created SOLR-4104:
-----------------------------------

             Summary: SolrCloudServer doesn't support multiple collections on same node
                 Key: SOLR-4104
                 URL: https://issues.apache.org/jira/browse/SOLR-4104
             Project: Solr
          Issue Type: Bug
          Components: clients - java, SolrCloud
    Affects Versions: 4.0
            Reporter: Jethro Bakker


We have got three solr instances and two collections which are replicated twice. So each solr instance has all the data available. 

The current implementation of CloudSolrServer has internal 6 slices but the end result is 3 urls which are passed to the load balancer. 
 
I think the problem is on the first line of the following code:

if (nodes.put(node, nodeProps) == null) {
  if (!sendToLeaders || (sendToLeaders && coreNodeProps.isLeader())) {
    String url = coreNodeProps.getCoreUrl();
    urlList2.add(url);
  } else if (sendToLeaders) {
    String url = coreNodeProps.getCoreUrl();
    replicas.add(url);
  }
}

The precondition of this code is that a node can contain one collection, which is not true.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org