Hi Shushuai,
Just a few thoughts.
I would guess that most people would argue for implementing
multi-tenancy within your core (via some unique filter ID) or collection
(via document routing) because of the headache of managing individual
cores at the scale you are talking about.
There are
-sharding to have multiple replicas of cores
(corresponding to tenants) across nodes?
Shushuai
From: Lajos la...@protulae.com
To: solr-user@lucene.apache.org
Sent: Saturday, March 15, 2014 5:37 AM
Subject: Re: Best practice to support multi-tenant with Solr
, March 15, 2014 5:37 AM
Subject: Re: Best practice to support multi-tenant with Solr
Hi Shushuai,
Just a few thoughts.
I would guess that most people would argue for implementing
multi-tenancy within your core (via some unique filter ID) or collection
(via document routing) because of the headache
:19 PM
Subject: Re: Best practice to support multi-tenant with Solr
Hi Shushuai,
---
Finally, I would (in general) argue for cloud-based implementations to give
you data redundancy ...
---
Do you mean using multi-sharding to have multiple
From: Lajos la...@protulae.com
To: solr-user@lucene.apache.org
Sent: Saturday, March 15, 2014 1:19 PM
Subject: Re: Best practice to support multi-tenant with Solr
Hi Shushuai,
---
Finally, I would (in general) argue for cloud-based implementations to give
: Saturday, March 15, 2014 11:18 AM
To: solr-user@lucene.apache.org
Subject: Re: Best practice to support multi-tenant with Solr
Hi Lajos, thanks again.
Your suggestion is to support multi-tenant via collection in a Solr Cloud:
putting small tenants in one collection and big tenants in their own
:
Subject: Re: Best practice to support multi-tenant with Solr
To: solr-user@lucene.apache.org
Date: Saturday, March 15, 2014, 5:59 PM
Hi Shushuai,
Yes, as Robi noted, you have to be careful with terminology:
core
generally refers to the traditional Solr configuration of a
single index
Hi,
I am looking into Solr 4.7 for best practice of multi-tenancy support. Our use
cases require support of thousands of tenants (say 10,000) and the incoming
data rate could be more than 10k documents per second. I did some research and
found people talked about scaling tenants at all four
