Frequently Asked Questions - SearchStax

The SearchStax® Frequently Asked Questions page includes the following approved question and answer about our Apache Solr Cloud services.

What is a collection/core/shard/replica?

Welcome to SearchStax. Sooner or later, everyone is confused by the distinctions among Solr index components. Here is a short glossary to help out.

Note: In Solr terminology, there is a sharp distinction between the logical parts of an index (collections, shards) and the physical manifestations of those parts (cores, replicas). Also, the definitions shift slightly between distributed and non-distributed collections, as noted below.

Cluster:

A SearchStax production deployment is usually a cluster of three nodes coordinated by a Zookeeper ensemble. Zookeeper ensures that changes to config files and to indexes are automatically distributed across the nodes of the cluster.

Node:

A single instance of Solr. In SearchStax deployments, one node corresponds to one physical server.

Collection:

A single logical index in its entirety, regardless of how many nodes it runs on or how many parts (shards) it has. One Solr node can serve multiple collections.

Shard:

A logical subset of the documents in a collection. A non-distributed collection has all documents in a single default shard. A distributed collection divides the documents among multiple shards.

Core:

A physical index on a node. In non-distributed collections, a core is the physical index of a single collection. In a distributed collection, each core includes only part of one index. Since a node can serve more than one collection, it can have more than one core.

Replica:

A physical index containing the documents of one logical shard. A distributed collection distributes these partial indexes across multiple nodes.

We love to answer questions!

Please contact the SearchStax Support Desk immediately if you have any question about Solr Cloud deployments.

Return to Frequently Asked Questions.