[
https://issues.apache.org/jira/browse/SOLR-4332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13560839#comment-13560839
]
Mark Miller commented on SOLR-4332:
-----------------------------------
It's not necessarily desired behavior, but it is known behavior. We have talked
about having a core act as a scatter-gather core in this case - and I've even
played around along those lines once. Never finished it though - one tricky
issue to deal with is if there are no cores...so should we just create a tmp
core to do the search?
It's basically in the future improvement bucket. Patches welcome though.
> Adding documents to SolrCloud collection broken when a node doesn't have a
> core for the collection
> --------------------------------------------------------------------------------------------------
>
> Key: SOLR-4332
> URL: https://issues.apache.org/jira/browse/SOLR-4332
> Project: Solr
> Issue Type: Bug
> Components: SolrCloud
> Affects Versions: 4.1
> Reporter: Eric Falcao
> Priority: Critical
>
> 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.
--
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: [email protected]
For additional commands, e-mail: [email protected]
