lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yonik Seeley (Commented) (JIRA)" <>
Subject [jira] [Commented] (SOLR-2880) Investigate adding an overseer that can assign shards, later do re-balancing, etc
Date Thu, 08 Dec 2011 18:19:40 GMT


Yonik Seeley commented on SOLR-2880:

bq. I didn't really like that compared to just passing a sys prop up front

That's what I'm proposing - that numShards not be stored anywhere in ZK at all.  Creation
of a new collection requires someone creating some initial nodes (i.e. the collection node
at a minimum).  Currently I believe this is just the bootstrapping code 

Scenario 1: autosharding
Whoever creates the new collection also creates a placeholder for each shard.  The current
bootstrapping code can look at a numShards system property, or a create collection API could
have a numShards parameter.

Scenario 2: custom sharding
Create the new collection as normal, but just don't create any placeholders for each shard.
 Adding a new shard is just 

We also shouldn't rely on the number of shards to split up the hash range (except initially
when creating a collection) - each shard should advertise what it's range is (in the case
of autosharding or sharding by hash).   This is important for future splitting of shards (i.e.
you could concurrently have shards that covers 0-9, 0-4, and 5-9)

So it seems like numShards is really just an input into new collection creation, not an intrinsic
property of the collection.
> Investigate adding an overseer that can assign shards, later do re-balancing, etc
> ---------------------------------------------------------------------------------
>                 Key: SOLR-2880
>                 URL:
>             Project: Solr
>          Issue Type: Sub-task
>          Components: SolrCloud
>            Reporter: Mark Miller
>            Assignee: Mark Miller
>             Fix For: 4.0
>         Attachments: SOLR-2880-merge-elections.patch, SOLR-2880.patch, SOLR-2880.patch

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


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

View raw message