lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yonik Seeley (Commented) (JIRA)" <>
Subject [jira] [Commented] (SOLR-2957) collection URLs in a cluster
Date Fri, 09 Dec 2011 17:48:40 GMT


Yonik Seeley commented on SOLR-2957:

Lookup core name directy as is done now.
If it's not found, and we are in ZK mode, then
return the core for a shard leader in the collection one exists, or
return the core for any shard in the collection.

What about the case where there isn't even a shard for the collection being requested?
It would seem desirable for a client to be able to hit any node in a cluster w/o worrying
about layout, movement, and rebalancing making requests suddenly fail.

One solution: if there's not a local core for the collection, convert the URL to add the collection
name as a parameter and then return the default core, which can then do the appropriate forwarding

> collection URLs in a cluster
> ----------------------------
>                 Key: SOLR-2957
>                 URL:
>             Project: Solr
>          Issue Type: Sub-task
>          Components: SolrCloud, update
>            Reporter: Yonik Seeley
>             Fix For: 4.0
> In solrcloud, one can hit a URL of /collection1/select and get a distributed search over
> If we wish to maintain this, we'll need some more flexible URL to core mapping since
there may be more than one core for the collection on a node, and the "collection1" core on
that node could go away altogether.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message