[SOLR-4332] Adding documents to SolrCloud collection broken when a node doesn't have a core for the collection

• Type: New Feature
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 4.1
• Component/s: SolrCloud
• Assignee: Mark Miller
• Reporter: Eric Falcao
• Created: 22/Jan/13 17:27
• Updated: 25/Feb/13 15:12
• Resolved: 25/Feb/13 15:12

Description

In SOLR-4321, it's documented that creating a collection via API results in some nodes having more than one core, while other nodes have zero cores.

Not sure if this is desired behavior, but when a node doesn't know about a core, it throws a 404 on select/update.

Reproduction:
-Create a 2 node SolrCloud cluster
-Create a new collection with numShards=1. 50% of your cluster will have a core for that collection.
-Do an update or select against the node that doesn't have the core. 404

Like I said, not sure if this is desired behavior, but I would expect a cluster of nodes to be able to forward requests appropriately to nodes that have a core for the collection.

Issue Links

• duplicates: SOLR-4210 Requests to a Collection that does not exist on the receiving node should be proxied to a suitable node.