[
https://issues.apache.org/jira/browse/SOLR-3755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shalin Shekhar Mangar updated SOLR-3755:
----------------------------------------
Attachment: SOLR-3755.patch
Patch updated over Mark's changes.
Changes:
1. Merged to latest trunk
2. New way of sub-shard replication in DistributedUpdatedProcessor
3. New operation "updateshardstate" in Overseer to change logical state of a
shard
4. Many bug fixes
5. A slightly better test -- still ways to go
Anshum and I have been collaborating on building this feature. Since the patch
was getting difficult to maintain without overwriting each others' changes, we
created a fork in github to develop this feature. The attached patch is a diff
against revision 1457757 of trunk (created by git).
The test case fails right now because the number of documents in sub-shards are
not correct (they are the same as the parent shard). Strangely, even if we
disable the index split part of the code, the number of documents in parent and
sub-shards are equal which makes me believe that there is a bug in core
creation or the way the test is setup. I'm looking into that right now.
The switch to make the parent shard in-active and the sub-shards active is also
not correct because it doesn't wait for the sub-shard replicas to recover
completely. We need to figure out a way to wait for replicas to be up and
running before we switch.
The way DUPF forwards updates to sub-shard replicas may also open us to race
conditions when we switch shard states.
> shard splitting
> ---------------
>
> Key: SOLR-3755
> URL: https://issues.apache.org/jira/browse/SOLR-3755
> Project: Solr
> Issue Type: New Feature
> Components: SolrCloud
> Reporter: Yonik Seeley
> Attachments: SOLR-3755-combined.patch,
> SOLR-3755-combinedWithReplication.patch, SOLR-3755-CoreAdmin.patch,
> SOLR-3755.patch, SOLR-3755.patch, SOLR-3755.patch, SOLR-3755.patch,
> SOLR-3755.patch, SOLR-3755-testSplitter.patch, SOLR-3755-testSplitter.patch
>
>
> We can currently easily add replicas to handle increases in query volume, but
> we should also add a way to add additional shards dynamically by splitting
> existing shards.
--
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
