[
https://issues.apache.org/jira/browse/SOLR-4114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13505496#comment-13505496
]
Per Steffensen commented on SOLR-4114:
--------------------------------------
bq. Per: this is unrelated to your patch of course - it just happened to come
up here.
No problem. I could make it as part of this patch if you want, but Im not sure
I agree with your way of interpreting the term "replication-factor". I would
expect "replication-factor" to say something about how many times the data is
REPLICATED. If I run with only one copy of the data for each slice, I would
logically say that my data is not replicated, and that matches the
replication-factor of 0.
I have used HDFS and HBase a little a year or so ago, but Im not sure what
meaning they put into the term "replica". I've also worked a lot with
ElasticSearch (which I believe is more of a pendant to Solr) and in
ElasticSearch I believe they use the term "replica" as the number of ADDITIONAL
copies of the data - equal to your/our current implementation in Solr.
> 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
>
>
> 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
