[ 
https://issues.apache.org/jira/browse/SOLR-4114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13509330#comment-13509330
 ] 

Mark Miller edited comment on SOLR-4114 at 12/3/12 11:35 PM:
-------------------------------------------------------------

Thanks for the corrected patch!

Two things I'd like to address before committing:

1. 
+    // nocommit
+    Thread.sleep(60000);
We have to do something else other than a one minute sleep in the test.

2. Setting the shard as part of the data dir.

I'd like the default data dir to remain /data. If you are not doing anything 
special that works fine.
I'd also like the ability to override the data dir on per shard basis, but I'm 
not sure what the best API for that is.

So I'd like to support what you want, but I don't want to change the default 
behavior.
                
      was (Author: markrmil...@gmail.com):
    Thanks for the updated patch.
Thanks for the corrected patch!

Two things I'd like to address before committing:

1. 
+    // nocommit
+    Thread.sleep(60000);
We have to do something else other than a one minute sleep in the test.

2. Setting the shard as part of the data dir.

I'd like the default data dir to remain /data. If you are not doing anything 
special that works fine.
I'd also like the ability to override the data dir on per shard basis, but I'm 
not sure what the best API for that is.

So I'd like to support what you want, but I don't want to change the default 
behavior.
                  
> Collection API: Allow multiple shards from one collection on the same Solr 
> server
> ---------------------------------------------------------------------------------
>
>                 Key: SOLR-4114
>                 URL: https://issues.apache.org/jira/browse/SOLR-4114
>             Project: Solr
>          Issue Type: New Feature
>          Components: multicore, SolrCloud
>    Affects Versions: 4.0
>         Environment: Solr 4.0.0 release
>            Reporter: Per Steffensen
>            Assignee: Per Steffensen
>              Labels: collection-api, multicore, shard, shard-allocation
>         Attachments: SOLR-4114.patch, SOLR-4114.patch, SOLR-4114.patch, 
> SOLR-4114_trunk.patch
>
>
> We should support running multiple shards from one collection on the same 
> Solr server - the run a collection with 8 shards on a 4 Solr server cluster 
> (each Solr server running 2 shards).
> Performance tests at our side has shown that this is a good idea, and it is 
> also a good idea for easy elasticity later on - it is much easier to move an 
> entire existing shards from one Solr server to another one that just joined 
> the cluter than it is to split an exsiting shard among the Solr that used to 
> run it and the new Solr.
> See dev mailing list discussion "Multiple shards for one collection on the 
> same Solr server"

--
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-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to