lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yonik Seeley (JIRA)" <>
Subject [jira] [Commented] (SOLR-4808) Persist and use replication factor and maxShardsPerNode at Collection and Shard level
Date Tue, 09 Jul 2013 18:49:49 GMT


Yonik Seeley commented on SOLR-4808:

bq. New mandatory "collectionApiMode" parameter during create collection command (we can think
of a better name)

Eh, internally mandatory I hope (as in, the user should not have to specify it?)

bq. replicationFactor is persisted at slice level

It still feels like this should be a collection level property that we have the ability to
store/override on a per-shard level.
The reasons off the top of my head:
 - would be nice to be able to create a new shard w/o having to know/specify what the replication
factor currently is
 - possible to completely lose the replication factor if we delete a shard and re-add a new
 - there may be one shard that has a lot of demand and you set it's replication level high...
so you override the replicationFactor for that shard only.  It would still be nice to be able
to adjust the replication factor for everyone else (by adjusting the collection level replicationFactor)

"maxShardsPerNode" - should that be maxReplicasPerNode, or are we really talking logical shards?

> Persist and use replication factor and maxShardsPerNode at Collection and Shard level
> -------------------------------------------------------------------------------------
>                 Key: SOLR-4808
>                 URL:
>             Project: Solr
>          Issue Type: New Feature
>          Components: SolrCloud
>            Reporter: Anshum Gupta
>            Assignee: Shalin Shekhar Mangar
>              Labels: solrcloud
>         Attachments: SOLR-4808.patch, SOLR-4808.patch
> The replication factor for a collection as of now is not persisted and used while adding
> We should save the replication factor at collection factor as well as shard level.

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:

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

View raw message