lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Miller (Commented) (JIRA)" <>
Subject [jira] [Commented] (SOLR-3088) create shard placeholders
Date Wed, 08 Feb 2012 20:44:59 GMT


Mark Miller commented on SOLR-3088:

I've actually been working on that right now because I need it for a test I'm writing.

What I realized pretty much immediately was that I needed a way to pass that param down the
chain so that the overseer eventually sees it. You should double check what I have done probably.
What I found is that it seems only the overseer looks at the numShards sys prop - so it won't
matter if its set on other nodes?

Anyway, what I settled for at the moment is, you can set the numShards on the cloud descriptor
- its not stored, so you may not always get it back in the future, it's just a startup param.
Then num_shards is also registered as part of the core state in zk - again it's only needed
once though. This lets us specify numShards per core though - which is kind of what you need
to support it in CoreAdminHandler.

Because the numShard will stay in the core_state, I'm not yet sure how that will work if you
end up being able to reshard by starting a core with a different number...
> create shard placeholders
> -------------------------
>                 Key: SOLR-3088
>                 URL:
>             Project: Solr
>          Issue Type: New Feature
>          Components: SolrCloud
>            Reporter: Yonik Seeley
>             Fix For: 4.0
> When creating a new collection, a placeholder for each shard should be created.

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