You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Shalin Shekhar Mangar (JIRA)" <ji...@apache.org> on 2013/03/11 17:45:23 UTC
[jira] [Updated] (SOLR-3755) shard splitting
[ 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-combined.patch
Attached is a first iteration of the patch. It is not working yet but a lot of the pieces required for this feature are coming together in this patch. Soon, I'd like to split it into smaller, committable issues/patches.
This is a very rough cut but any comments/suggestions on the general approach and/or the patch will be very helpful.
Changes:
* OverseerCollectionProcessor has a new command called splitshard which executes the whole strategy
* Implicit support for creating new shards (by creating a core with a new shard in "construction" state)
* "Construction" state is introduced for shards
* CoreAdmin has a new APPLYBUFFEREDUPDATES task which, as the name says, instructs a core to apply all buffered updates
TODO:
* Create replicas for new sub-shards
* Figure out how and where to set sub-shards as active and divert traffic away from parent shard
* Tests (both unit and ChaosMonkey based)
Right now, I'm running into a bug where the first sub-shard creation goes through but the second sub-shard coreadmin "CREATE" command blocks in .ShardLeaderElectionContext.waitForReplicasToComeUp(ElectionContext.java:326)
Can anyone tell me what I've overlooked?
> 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-CoreAdmin.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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org