Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: solr-user@lucene.apache.org
Received-SPF: pass (nike.apache.org: domain of goksron@gmail.com designates
 74.125.82.176 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=kgD+I2Fg9rNArqKBkN6+UoX7t1XJStyGOGNWpBTYNjnzCGao/kaeNNsTbOe2nckaTB
         k3hiZ0ON4n0glUFQCRDqg8MvjQdyJkf2PG+w27aymDp+n/D7pTa0X6oNYjCJkYf8wWtE
         i3sIOONFiVHlVA4sqDaeNmoXk/jIbuUbmE2V4=
MIME-Version: 1.0
In-Reply-To: <AANLkTi=QSQM2fUyHiWPT2ZJE4XAVKWW9pqnH9u-7KDMs@mail.gmail.com>
References: <AANLkTinbP+8973PVNSxCj20TfxKOVYLb2DuSy1WpfMXP@mail.gmail.com>
	<AANLkTi=QSQM2fUyHiWPT2ZJE4XAVKWW9pqnH9u-7KDMs@mail.gmail.com>
Date: Tue, 12 Oct 2010 14:14:37 -0700
Message-ID: <AANLkTi=VBtwfUL4mGbPJOe8WKzPESav5AXzX-QxdGT2Z@mail.gmail.com>
Subject: Re: multi cores vs filter queries for a multi tenant deployment
From: Lance Norskog <goksron@gmail.com>
To: solr-user@lucene.apache.org
Content-Type: text/plain; charset=UTF-8

For multi-tenant, all customers share the same words for text fields.
A customer's search relevance might be useless.

Also, spelling & autosuggest recommendations come from all of the
entries in a field, so the customers can see each other's words.
There are other quirks in memory and cache management. And taking
updates.

1 core/tenant has operational scripting problems. You'll have to write
all your own ops software, there is no help.

Lance

On Tue, Oct 12, 2010 at 2:59 AM, Tharindu Mathew <mccloud35@gmail.com> wrote:
> Basically, for a large number of users would using a single index or using a
> multi core approach be better?
>
> On Tue, Oct 12, 2010 at 11:39 AM, Tharindu Mathew <mccloud35@gmail.com>wrote:
>
>> Hi everyone,
>>
>> I'm sort of looking in to a deployment which will support multi tenancy.
>> This means that there will be 1000s of tenant domains each having 1000s of
>> users. I need to figure out which approach is better for this deployment
>> when using the solr server.
>>
>> Approach #1 - Use multi cores for each tenant and thereby use separate
>> indexes for each. If necessary use filter queries with user ids for users.
>> Approach #2 - Use filter queries with tenant ids to filter out results of
>> different tenant domains. Similarly, as above, use user ids as needed.
>>
>> My concern comes on aspects of performance and security.
>>
>> Will using approach #1 be a killer for performance? With this many number
>> of users, this setup has to scale smoothly for so many number of users. When
>> the deployment potentially will have 1000s of cores, how can I prevent a
>> security vulnerability appearing between cores?
>>
>> What are the implications of using approach #2? Will I have to constantly
>> check around for code with security checks since only a single index is
>> used?
>>
>> Any feedback for the above concerns would be really appreciated.
>>
>> Thanks in advance.
>>
>> --
>> Regards,
>>
>> Tharindu
>>
>
>
>
> --
> Regards,
>
> Tharindu
>


-- 
Lance Norskog
goksron@gmail.com