lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Darren Govoni <dar...@ontrenet.com>
Subject Re: Cloud terminology clarification
Date Sun, 09 Sep 2012 10:07:04 GMT
I agree it needs updating and I've always gotten confused at some point
by
the use (misuse) of terms.

For example, the term 'node' is thrown around a lot too. What is it??!
Hehe.

On Sat, 2012-09-08 at 22:26 -0700, JesseBuesking wrote:

> It's been a while since the terminology at
> http://wiki.apache.org/solr/SolrTerminology has been updated, so I'm
> wondering how these terms apply to solr cloud setups.
> 
> My take on what the terms mean:
> 
> Collection: Basically the highest level container that bundles together the
> other pieces for servicing a particular search setup
> Core: An individual solr instance (represents entire indexes)
> Shard: A portion of a core (represents a subset of an index)
> 
> Therefore:
> - increasing the number of shards allows for indexing more documents (aka
> scaling the amount of data that can be indexed)
> - increasing the number of cores increases the potential throughput of
> requests (aka cores mirror each other allowing you to distribute requests to
> multiple servers)
> 
> Does this sound right?
> 
> If so, then my follow up question would be does the following directory
> structure look right/standard?
> 
> .../solr # = solr home
> .../solr/collection-01
> .../solr/collection-01/core-01
> .../solr/collection-01/core-02
> 
> And if this is right, I'm on a roll :D
> 
> My next question would then be:
> Given we're using zookeeper (separate machine), do we need 1 conf folder at
> collection-01's level?  Or do we need 1 conf folder per core?
> 
> 
> 
> --
> View this message in context: http://lucene.472066.n3.nabble.com/Cloud-terminology-clarification-tp4006407.html
> Sent from the Solr - User mailing list archive at Nabble.com.



Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message