[
https://issues.apache.org/jira/browse/SOLR-1277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12785381#action_12785381
]
Mark Miller edited comment on SOLR-1277 at 12/3/09 4:18 PM:
------------------------------------------------------------
bq. less required configuration please.
You wouldn't have to configure anything. Ideally, the example would come with
it simply configured for one core with everything how it works now (same urls,
etc). Optionally, we could allow someone to not use it, and just assume that
simple configuration. The example would want it though, so we can put in
commented out example config (eg for zookeeper setup). Then if you didnt have
it, we would essentially read a dummy simple cfg (though I don't think thats
really necessary myself), and we can have singlecore/multicore more in line
with each other.
There is no getting around the config we are looking for - zookeeper will need
it one way or another, and not in solrconfig.
*edit*
Of course, you could say using multicore is required for zookeeper - but its an
odd artificial limitation. Having multi-core subsume single core in a more
seamless is a nice goal in either case.
was (Author: markrmil...@gmail.com):
bq. less required configuration please.
You wouldn't have to configure anything. Ideally, the example would come with
it simply configured for one core with everything how it works now (same urls,
etc). Optionally, we could allow someone to not use it, and just assume that
simple configuration. The example would want it though, so we can put in
commented out example config (eg for zookeeper setup). Then if you didnt have
it, we would essentially read a dummy simple cfg (though I don't think thats
really necessary myself), and we can have singlecore/multicore more in line
with each other.
There is no getting around the config we are looking for - zookeeper will need
it one way or another, and not in solrconfig.
> 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.
