lucene - Solr Collection vs Cores

Question

I struggle with understanding the difference between collections and cores. If I understand it correctly, cores are multiple indexes. Collection consists of cores, so essentially they share the same logic in separation, i.e. separate cores and collections have separate end-points.

I have the following scenario. I create a backend for cloud service for several online shops. Each shop has a set of products, to which customers can add reviews. I want to index static data (product information) separately from dynamic information(reviews) so I can improve performance.

How can I best separate in Solr???

Answer 1

From the SolrCloud Documentation

Collection: A single search index.

Shard: A logical section of a single collection (also called Slice). Sometimes people will talk about "Shard" in a physical sense (a manifestation of a logical shard)

Replica: A physical manifestation of a logical Shard, implemented as a single Lucene index on a SolrCore

Leader: One Replica of every Shard will be designated as a Leader to coordinate indexing for that Shard

SolrCore: Encapsulates a single physical index. One or more make up logical shards (or slices) which make up a collection.

Node: A single instance of Solr. A single Solr instance can have multiple SolrCores that can be part of any number of collections.

Cluster: All of the nodes you are using to host SolrCores.

So basically a Collection (Logical group) has multiple cores (physical indexes).

Also, check the discussion