You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Yonik Seeley (Created) (JIRA)" <ji...@apache.org> on 2011/12/09 18:40:40 UTC
[jira] [Created] (SOLR-2957) collection URLs in a cluster
collection URLs in a cluster
----------------------------
Key: SOLR-2957
URL: https://issues.apache.org/jira/browse/SOLR-2957
Project: Solr
Issue Type: Sub-task
Reporter: Yonik Seeley
In solrcloud, one can hit a URL of /collection1/select and get a distributed search over collection1.
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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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
[jira] [Commented] (SOLR-2957) collection URLs in a cluster
Posted by "Yonik Seeley (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-2957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13166361#comment-13166361 ]
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 logic.
> collection URLs in a cluster
> ----------------------------
>
> Key: SOLR-2957
> URL: https://issues.apache.org/jira/browse/SOLR-2957
> 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 collection1.
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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
[jira] [Commented] (SOLR-2957) collection URLs in a cluster
Posted by "Yonik Seeley (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-2957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13204703#comment-13204703 ]
Yonik Seeley commented on SOLR-2957:
------------------------------------
cool! +1
> collection URLs in a cluster
> ----------------------------
>
> Key: SOLR-2957
> URL: https://issues.apache.org/jira/browse/SOLR-2957
> Project: Solr
> Issue Type: Sub-task
> Components: SolrCloud, update
> Reporter: Yonik Seeley
> Assignee: Mark Miller
> Fix For: 4.0
>
> Attachments: SOLR-2957.patch
>
>
> In solrcloud, one can hit a URL of /collection1/select and get a distributed search over collection1.
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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
[jira] [Updated] (SOLR-2957) collection URLs in a cluster
Posted by "Mark Miller (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-2957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Miller updated SOLR-2957:
------------------------------
Attachment: SOLR-2957.patch
I've implemented the first part - if you pass a corename in the url that is not found, when in zk mode, we try using the corename as the collection name and we search the local instance for any cores that are in that collection, first looking for a leader.
> collection URLs in a cluster
> ----------------------------
>
> Key: SOLR-2957
> URL: https://issues.apache.org/jira/browse/SOLR-2957
> Project: Solr
> Issue Type: Sub-task
> Components: SolrCloud, update
> Reporter: Yonik Seeley
> Assignee: Mark Miller
> Fix For: 4.0
>
> Attachments: SOLR-2957.patch
>
>
> In solrcloud, one can hit a URL of /collection1/select and get a distributed search over collection1.
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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
[jira] [Assigned] (SOLR-2957) collection URLs in a cluster
Posted by "Mark Miller (Assigned) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-2957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Miller reassigned SOLR-2957:
---------------------------------
Assignee: Mark Miller
> collection URLs in a cluster
> ----------------------------
>
> Key: SOLR-2957
> URL: https://issues.apache.org/jira/browse/SOLR-2957
> Project: Solr
> Issue Type: Sub-task
> Components: SolrCloud, update
> Reporter: Yonik Seeley
> Assignee: Mark Miller
> Fix For: 4.0
>
>
> In solrcloud, one can hit a URL of /collection1/select and get a distributed search over collection1.
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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
[jira] [Commented] (SOLR-2957) collection URLs in a cluster
Posted by "Mark Miller (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-2957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13204692#comment-13204692 ]
Mark Miller commented on SOLR-2957:
-----------------------------------
I'm going to commit this (if there are no objections/comments) and create another issue for the further improvement of working even when there are no nodes for the collection on the local instance.
> collection URLs in a cluster
> ----------------------------
>
> Key: SOLR-2957
> URL: https://issues.apache.org/jira/browse/SOLR-2957
> Project: Solr
> Issue Type: Sub-task
> Components: SolrCloud, update
> Reporter: Yonik Seeley
> Assignee: Mark Miller
> Fix For: 4.0
>
> Attachments: SOLR-2957.patch
>
>
> In solrcloud, one can hit a URL of /collection1/select and get a distributed search over collection1.
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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
[jira] [Resolved] (SOLR-2957) collection URLs in a cluster
Posted by "Mark Miller (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-2957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Miller resolved SOLR-2957.
-------------------------------
Resolution: Fixed
I've got a new issue for the remaining suggestion: SOLR-3119
> collection URLs in a cluster
> ----------------------------
>
> Key: SOLR-2957
> URL: https://issues.apache.org/jira/browse/SOLR-2957
> Project: Solr
> Issue Type: Sub-task
> Components: SolrCloud, update
> Reporter: Yonik Seeley
> Assignee: Mark Miller
> Fix For: 4.0
>
> Attachments: SOLR-2957.patch
>
>
> In solrcloud, one can hit a URL of /collection1/select and get a distributed search over collection1.
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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