[
https://issues.apache.org/jira/browse/SOLR-5025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13704237#comment-13704237
]
Shawn Heisey commented on SOLR-5025:
------------------------------------
I looked around for an existing issue before filing this, didn't see one.
> Implement true re-sharding for SolrCloud
> ----------------------------------------
>
> Key: SOLR-5025
> URL: https://issues.apache.org/jira/browse/SOLR-5025
> Project: Solr
> Issue Type: Wish
> Components: SolrCloud
> Reporter: Shawn Heisey
>
> Shard splitting is an incredibly nice thing to have, but it doesn't
> completely address the idea of re-sharding.
> Let's say that you currently have three shards, only your index is three or
> four times as big as you ever expected it to get when you first built it.
> You've added nodes, which helps, but doesn't address the fundamental fact
> that each of your shards is too big for an individual server. If you had
> created eight shards up front, everything would be smooth. It's not possible
> with shard splitting to go from three equal size shards to eight equal size
> shards.
> A new feature to accomplish true re-sharding would solve this. One
> implementation possibility: Create a new collection with the new numShards,
> split all the documents accordingly to the new replicas, then rename/swap the
> collection and core names.
> There are a number of sticky points to iron out regardless of the
> implementation method chosen, some of which could be really hairy.
--
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: [email protected]
For additional commands, e-mail: [email protected]
