You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-user@lucene.apache.org by JesseBuesking <je...@gmail.com> on 2012/09/09 07:26:13 UTC
Cloud terminology clarification
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.
Re: Cloud terminology clarification
Posted by JesseBuesking <je...@gmail.com>.
Thanks for the replies!
@Mark you mention running multiple cores on a single node. How would you go
about configuring that?
http://lucene.472066.n3.nabble.com/Starting-multiple-cores-shards-on-a-single-node-td4007526.html
--
View this message in context: http://lucene.472066.n3.nabble.com/Cloud-terminology-clarification-tp4006407p4008095.html
Sent from the Solr - User mailing list archive at Nabble.com.
Re: Cloud terminology clarification
Posted by Mark Miller <ma...@gmail.com>.
For me, a node is a single Solr instance - generally this is one per machine. A single Solr instance (or node) may have multiple cores.
Configuration is per collection, not per SolrCore - unless if course if your collection is one shard with no replicas - then I guess you could say it was per core.
Sent from my iPhone
On Sep 9, 2012, at 6:07 AM, Darren Govoni <da...@ontrenet.com> wrote:
> 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.
>
>
Re: Cloud terminology clarification
Posted by Darren Govoni <da...@ontrenet.com>.
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.