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] [Commented] (SOLR-3755) shard splitting
Date Mon, 03 Sep 2012 19:53:08 GMT

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

Yonik Seeley commented on SOLR-3755:
------------------------------------

It seems like we need logical shard parameters (i.e. Slice class), but we don't currently
have a place for them.
These parameters would include:
 - collection (this is somewhat redundant, but belongs more on a slice than on a replica)
 - replication factor (i.e. in time based sharding, one may want more replicas of recent shards
to handle greater query throughput)
 - hash range(s) covered by the slice
 - maybe a pointer to the leader, rather than having to search through the nodes?

You can see the previous structure of cloudstate from my previous message.

One fix is to introduce a "nodes" or "replicas" level to contain the nodes and leave the other
properties as top-level:

{code}
  "shard1": {
    "replication_factor" : 3,
    "range" : "00000000-3fffffff",
    "nodes" : {
      "Rogue:8983_solr_collection1":{
        "state" : "active"
      }
    }
  }
{code}

Another way is to introduce a "props" to store properties:

{code}
  "shard1": {
    "props" : {
      "replication_factor" : 3,
      "range" : "00000000-3fffffff"
    },
    "Rogue:8983_solr_collection1":{
      "state" : "active"
    }
  }
{code}

The first option feels more natural to me - properties are directly under the shard, and the
nodes of a shard are simply another property.
                
> 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.patch, SOLR-3755.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


Mime
View raw message