[
https://issues.apache.org/jira/browse/SOLR-4808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13692098#comment-13692098
]
Shalin Shekhar Mangar edited comment on SOLR-4808 at 6/24/13 4:12 PM:
----------------------------------------------------------------------
Here's what I have in mind:
SolrCloud shall store the following two properties in addition to the ones it
already does:
# smartCloud (boolean) - Stored per collection
# autoManageCluster - Stored per collection
# maxShardsPerNode - Stored per collection
# replicationFactor - Stored per slice
The smartCloud parameter must be specified in the create collection API. The
smartCloud mode will default to false for all existing collections. The
autoManageCluster, maxShardsPerNode and replicationFactor properties will be
used in SolrCloud only if smartCloud=true for that collection.
If a collection is running in smart mode then it will assume the cluster state
in ZK to be the truth i.e. it may re-assign pre-configured cores when they
join/re-join the cluster.
If autoManageCluster=true then Overseer will attempt to keep the cluster
running according to the values of replication factor and maxShardsPerNode i.e.
it will increase/decrease replicas to match replication factor and
maxShardsPerNode
A new “editcollection” API will be introduced to:
Modify value of smartCloud
Modify value of autoManageCluster
Modify values of maxShardsPerNode for the collection
Modify value of replicationFactor for entire collection (apply to each and
every slice)
Modify values of replicationFactor on a per-slice basis
The way to add a node to the collection would be to 1) increase the replication
factor (of a collection or shard) and then 2) start a node
The smartCloud property can be turned off via editcollection to allow users to
pre-configure nodes if they want to.
I'm not working on the "autoManageCluster" right now. I welcome suggestions for
alternate names of the "smartCloud" property.
was (Author: shalinmangar):
Here's what I have in mind:
SolrCloud shall store the following two properties in addition to the ones it
already does:
# smartCloud (boolean) - Stored per collection
# autoManageCluster - Stored per collection
# maxShardsPerNode - Stored per collection
# replicationFactor - Stored per slice
The smartCloud parameter must be specified in the create collection API. The
smartCloud mode will default to false for all existing collections. The
autoManageCluster, maxShardsPerNode and replicationFactor properties will be
used in SolrCloud only if smartCloud=true for that collection.
If a collection is running in smart mode then it will assume the cluster state
in ZK to be the truth i.e. it may re-assign pre-configured cores when they
join/re-join the cluster.
If autoManageCluster=true then Overseer will attempt to keep the cluster
running according to the values of replication factor and maxShardsPerNode i.e.
it will increase/decrease replicas to match replication factor and
maxShardsPerNode
A new “editcollection” API will be introduced to:
Modify value of smartCloud
Modify value of autoManageCluster
Modify values of maxShardsPerNode for the collection
Modify value of replicationFactor for entire collection (apply to each and
every slice)
Modify values of replicationFactor on a per-slice basis
The way to add a node to the collection would be to 1) increase the replication
factor (of a collection or shard) and then 2) start a node
The smartCloud property can be turned off via editcollection to allow users to
pre-configure nodes if they want to.
I'm not working on the "autoManageCluster" right now. I welcome suggestions for
the "smartCloud" property.
> Persist and use replication factor at Collection and Shard level
> ----------------------------------------------------------------
>
> Key: SOLR-4808
> URL: https://issues.apache.org/jira/browse/SOLR-4808
> Project: Solr
> Issue Type: New Feature
> Components: SolrCloud
> Reporter: Anshum Gupta
> Assignee: Shalin Shekhar Mangar
> Labels: solrcloud
>
> The replication factor for a collection as of now is not persisted and used
> while adding replicas.
> 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: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
