Type: New Feature
Affects Version/s: 4.1
Fix Version/s: None
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.
-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.