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

Patrick Hunt commented on SOLR-1277:
------------------------------------

Hi phunt here from ZK team, let me say that we are psyched to see you 
considering use of ZK in solr! Feel
free to ping us http://hadoop.apache.org/zookeeper/mailing_lists.html if you 
have any questions.

One suggestion, you may want a solr specific root:

/solr/${solr.domain}/.... 

(prefix with /solr) so that if end users want to use ZK for things in addition 
to solr they can setup
a single zk cluster and still have information segregated nicely.

You can always use zk client's  "chroot" feature when connecting, this would 
map /solr as / from the perspective
of the clients. You might consider chrooting /solr/${solr.domain} if the client 
for ${solr.domain}
only looks at data from it's domain.

> 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.

Reply via email to