[
https://issues.apache.org/jira/browse/SOLR-1277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12785403#action_12785403
]
Yonik Seeley commented on SOLR-1277:
------------------------------------
bq. What I'm suggesting here is a little different though - that Solr.xml
allows a core config that acts like single core now - a core name of "" and an
instance dir of "" or "." that sets everything to work as single core now.
I like the idea - but worry about the details of managing it with core admin
with a name of "" (I think the SolrParams class that handles HTTP params treats
zero length params as a null - as if it hasn't been passed. I believe this was
done to support forms).
bq. but if you want to use zookeeper with singlecore, add the solr.xml and
setup the required config
My first thought was that it should be possible to store pretty much everything
in zookeeper... but then again - the nodes (solr servers) contain the actual
indexes, so we should probably persist information about that at least.
Still seems like it would be nice to start a solr server and point it at a
cluster, w/o the need to write a solr.xml file for it. Solr could then write
out a solr.xml with the needed info. This would be useful for adding a new
server to a cluster.
> 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, SOLR-1277.patch,
> SOLR-1277.patch, zookeeper-3.2.1.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.
