lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yonik Seeley (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (SOLR-3755) shard splitting
Date Tue, 28 Aug 2012 19:53:07 GMT

    [ https://issues.apache.org/jira/browse/SOLR-3755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13440698#comment-13440698
] 

Yonik Seeley edited comment on SOLR-3755 at 8/29/12 6:51 AM:
-------------------------------------------------------------

We need to associate hash ranges with shards and allow overlapping shards (i.e. 1-10, 1-5,6-10)

General Strategy for splitting w/ no service interruptions:
 - Bring up 2 new cores on the same node, covering the new hash ranges
 - Both cores should go into recovery mode (i.e. leader should start
forwarding updates)
   - leaders either need to consider these new smaller shards as replicas, or they need to
forward to the "leader" for the new smaller shard
   - searches should no longer go across all shards, but should just span the complete hash
range
 - leader does a hard commit and splits the index
 - Smaller indexes are installed on the new cores
 - Overseer should create new replicas for new shards
 - Mark old shard as “retired” – some mechanism to shut it down (after there is an acceptable
amount of coverage of the new shards via replicas)

Future: allow splitting even with “custom” shards
                
      was (Author: yseeley@gmail.com):
    We need to associate hash ranges with shards and allow overlapping shards (i.e. 1-10,
1-5,6-10)

General Strategy for splitting w/ no service interruptions:
 - Bring up 2 new cores on the same node, covering the new hash ranges
 - Both cores should go into recovery mode (i.e. leader should start
forwarding updates)
 - leader does a hard commit and splits the index
 - Smaller indexes are installed on the new cores
 - Overseer should create new replicas for new shards
 - Mark old shard as “retired” – some mechanism to shut it down (after there is an acceptable
amount of coverage of the new shards via replicas)

Future: allow splitting even with “custom” shards
                  
> 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
>
> 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


Mime
View raw message