You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Jethro Bakker (JIRA)" <ji...@apache.org> on 2012/11/21 22:44:57 UTC
[jira] [Created] (SOLR-4104) SolrCloudServer doesn't support
multiple collections on same node
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
[jira] [Updated] (SOLR-4104) SolrCloudServer doesn't support
multiple collections on same node
Posted by "Jethro Bakker (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-4104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jethro Bakker updated SOLR-4104:
--------------------------------
Description:
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 6 slices in my setup 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:
{noformat}
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);
}
}
{noformat}
The precondition of this code is that a node can contain one collection, which is not true. Urls are only added when the hashmap 'nodes' does not already contain the node.
was:
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 6 slices in my setup 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:
{noformat}
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);
}
}
{noformat}
The precondition of this code is that a node can contain one collection, which is not true.
> 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 6 slices in my setup 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:
> {noformat}
> 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);
> }
> }
> {noformat}
> The precondition of this code is that a node can contain one collection, which is not true. Urls are only added when the hashmap 'nodes' does not already contain the node.
--
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
[jira] [Updated] (SOLR-4104) SolrCloudServer doesn't support
multiple collections on same node
Posted by "Jethro Bakker (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-4104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jethro Bakker updated SOLR-4104:
--------------------------------
Description:
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 6 slices in my setup 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.
was:
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.
> 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 6 slices in my setup 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
[jira] [Updated] (SOLR-4104) SolrCloudServer doesn't support
multiple collections on same node
Posted by "Jethro Bakker (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-4104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jethro Bakker updated SOLR-4104:
--------------------------------
Description:
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 6 slices in my setup 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:
{noformat}
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.
was:
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 6 slices in my setup 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.
> 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 6 slices in my setup 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:
> {noformat}
> 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
[jira] [Closed] (SOLR-4104) SolrCloudServer doesn't support
multiple collections on same node
Posted by "Jethro Bakker (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-4104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jethro Bakker closed SOLR-4104.
-------------------------------
Resolution: Not A Problem
> 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 6 slices in my setup 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:
> {noformat}
> 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);
> }
> }
> {noformat}
> The precondition of this code is that a node can contain one collection, which is not true. Urls are only added when the hashmap 'nodes' does not already contain the node.
--
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
[jira] [Updated] (SOLR-4104) SolrCloudServer doesn't support
multiple collections on same node
Posted by "Jethro Bakker (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-4104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jethro Bakker updated SOLR-4104:
--------------------------------
Description:
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 6 slices in my setup 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:
{noformat}
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);
}
}
{noformat}
The precondition of this code is that a node can contain one collection, which is not true.
was:
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 6 slices in my setup 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:
{noformat}
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.
> 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 6 slices in my setup 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:
> {noformat}
> 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);
> }
> }
> {noformat}
> 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