[
https://issues.apache.org/jira/browse/SOLR-2595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13049703#comment-13049703
]
Shalin Shekhar Mangar commented on SOLR-2595:
---------------------------------------------
Example: Lets say you have a core C1 on host H1 which you want to split and
move a part of the index to core C2 on host H2
The sequence of operation can be:
# Use SOLR-2593 to split C1 and move the part to be migrated into a temporary
core, say "S"
# Create a temporary core on H2 host, say "T"
# Assign "T" to be a slave of "S"
# When replication completes, use SOLR-2596 to merge "T" into "C2" - perhaps
update some ZK flags so that
Some details still need to be figured out e.g.
* What strategy to use for splitting?
* How to delete the migrated part from the source index?
* How to update the shard lookup and distributed indexing schemes for the
migrated part?
* What happens to writes during the migration? Should we disallow it?
> Split and migrate indexes
> -------------------------
>
> Key: SOLR-2595
> URL: https://issues.apache.org/jira/browse/SOLR-2595
> Project: Solr
> Issue Type: New Feature
> Components: multicore, replication (java), SolrCloud
> Reporter: Shalin Shekhar Mangar
> Fix For: 4.0
>
>
> When an shard's index grows too large or a shard becomes too loaded, it
> should be possible to split parts of a shard's index and migrate/merge to a
> less loaded node.
--
This message is automatically generated by JIRA.
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
