[
https://issues.apache.org/jira/browse/SOLR-1277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12789121#action_12789121
]
Noble Paul edited comment on SOLR-1277 at 12/11/09 5:43 AM:
------------------------------------------------------------
A few comments on the http://wiki.apache.org/solr/SolrCloud#Layout
When we talk about zookeeper schema We have to add more data on what are the
contents. such as,
* What is the node type ? (ephemeral|sequential etc)
* What is the node data?
What does the config look like? mycluster/configs/collection1_config/v1/
What are these? solrconfig.xml, schema.xml, stopwords.txt, etc
* are they nodes? if yes, of what type?
* What is the data?
contents of
/collections/collection1/shards
localhost:8983/solr/collection1=shardX,shardY,shardZ
localhost:7574/solr/collection1=shardX,shardZ
what are these ? nodes ? what is the data?
Moreover we need to document on how the configuration on
solr.xml/solrconfig.xml will look like so that we know which component consumes
what information
was (Author: noble.paul):
A few comments on the http://wiki.apache.org/solr/SolrCloud#Layout
When we talk about zookeeper schema We have to add more data on what are the
contents. such as,
* What is the node type ? (ephemeral|sequential etc)
* What is the node data?
What does the config look like? mycluster/configs/collection1_config/v1/
What are these? solrconfig.xml, schema.xml, stopwords.txt, etc
* are they nodes? if yes, of what type?
* What is the data?
contents of
/collections/collection1/shards
localhost:8983/solr/collection1=shardX,shardY,shardZ
localhost:7574/solr/collection1=shardX,shardZ
what are these ? nodes ? what is the data?
> 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, 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.
