[jira] Issue Comment Edited: (SOLR-1277) Implement a Solr specific naming service (using Zookeeper)

["Noble Paul (JIRA)" <ji...@apache.org>]

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

Noble Paul edited comment on SOLR-1277 at 11/11/09 8:55 AM:
------------------------------------------------------------

 I propose a hierarchical node structure in ZooKeeper. 

eg:

{code}
/<zookeeper_rootdir>
       ${solr.domain}
           /shard1
                  /master -> url=myurl:8080,rep_url=/replication,a=b,c=d
                   /slave
                          /slave00 -> url=myurl:8080,a=b,c=d
                          /slave00 -> url=myurl:8080,a=b,c=d                                                     
{code}

Master is only one. so we can have a special node.
Slaves are many. So, we can use a sequential node name . Zookeeper will take care of assigning a name . We can add data such as url etc as the node data. 

We must be able to use the same zookeeper component for distributed search for discovering other shards .SOLR-1431 can have a zookeeper based implementation too
          
                        
                               



      was (Author: noble.paul):
     I propose a hierarchical node structure in ZooKeeper. 

eg:

{code}
/<zookeeper_rootdir>
       ${solr.domain}
           /shard1
                  /master -> url=myurl:8080,rep_url=/replication,a=b,c=d
           /slave
                  /slave00 -> url=myurl:8080,a=b,c=d
                  /slave00 -> url=myurl:8080,a=b,c=d                                                     
{code}

Master is only one. so we can have a special node.
Slaves are many. So, we can use a sequential node name . Zookeeper will take care of assigning a name . We can add data such as url etc as the node data. 

We must be able to use the same zookeeper component for distributed search for discovering other shards .SOLR-1431 can have a zookeeper based implementation too
          
                        
                               


  
> Implement a Solr specific naming service (using Zookeeper)
> ----------------------------------------------------------
>
>                 Key: SOLR-1277
>                 URL: https://issues.apache.org/jira/browse/SOLR-1277
>             Project: Solr
>          Issue Type: New Feature
>    Affects Versions: 1.4
>            Reporter: Jason Rutherglen
>            Assignee: Grant Ingersoll
>            Priority: Minor
>             Fix For: 1.5
>
>         Attachments: log4j-1.2.15.jar, SOLR-1277.patch, zookeeper-3.2.0.jar
>
>   Original Estimate: 672h
>  Remaining Estimate: 672h
>
> The goal is to give Solr server clusters self-healing attributes
> where if a server fails, indexing and searching don't stop and
> all of the partitions remain searchable. For configuration, the
> ability to centrally deploy a new configuration without servers
> going offline.
> We can start with basic failover and start from there?
> Features:
> * Automatic failover (i.e. when a server fails, clients stop
> trying to index to or search it)
> * Centralized configuration management (i.e. new solrconfig.xml
> or schema.xml propagates to a live Solr cluster)
> * Optionally allow shards of a partition to be moved to another
> server (i.e. if a server gets hot, move the hot segments out to
> cooler servers). Ideally we'd have a way to detect hot segments
> and move them seamlessly. With NRT this becomes somewhat more
> difficult but not impossible?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.