[SOLR-1277] Implement a Solr specific naming service (using Zookeeper)

• Type: New Feature
• Status: Closed
• Priority: Minor
• Resolution: Won't Fix
• Affects Version/s: 1.4
• Fix Version/s: 3.2
• Assignee: Grant Ingersoll
• Reporter: Jason Rutherglen
• Created: 14/Jul/09 17:41
• Updated: 02/May/13 02:29
• Resolved: 30/Jun/10 19:07

Description

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?

Issue Links

• depends upon: SOLR-1621 Allow current single core deployments to be specified by solr.xml
• depends upon: SOLR-1585 Refactor shards handling out of QueryComponent and into ShardsComponent
• is blocked by: SOLR-1431 CommComponent abstracted
• is blocked by: SOLR-1237 firstSearcher and newSearcher should identify themselves via the parameter set passed in
• is related to: SOLR-1663 Add numRequests to SolrCore statistics to make it easier to track load
• is related to: SOLR-1698 load balanced distributed search