You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Mark Miller (JIRA)" <ji...@apache.org> on 2013/02/25 16:10:14 UTC

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

     [ https://issues.apache.org/jira/browse/SOLR-4332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mark Miller updated SOLR-4332:
------------------------------

      Assignee: Mark Miller
      Priority: Major  (was: Critical)
    Issue Type: New Feature  (was: Bug)
    
> 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: New Feature
>          Components: SolrCloud
>    Affects Versions: 4.1
>            Reporter: Eric Falcao
>            Assignee: Mark Miller
>
> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org