Return-Path: Delivered-To: apmail-lucene-solr-user-archive@minotaur.apache.org Received: (qmail 55559 invoked from network); 25 Apr 2010 11:50:20 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 25 Apr 2010 11:50:20 -0000 Received: (qmail 62075 invoked by uid 500); 25 Apr 2010 11:50:17 -0000 Delivered-To: apmail-lucene-solr-user-archive@lucene.apache.org Received: (qmail 62018 invoked by uid 500); 25 Apr 2010 11:50:17 -0000 Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: solr-user@lucene.apache.org Delivered-To: mailing list solr-user@lucene.apache.org Received: (qmail 62010 invoked by uid 99); 25 Apr 2010 11:50:16 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 25 Apr 2010 11:50:16 +0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=AWL,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of shalinmangar@gmail.com designates 209.85.221.177 as permitted sender) Received: from [209.85.221.177] (HELO mail-qy0-f177.google.com) (209.85.221.177) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 25 Apr 2010 11:50:10 +0000 Received: by qyk7 with SMTP id 7so284516qyk.14 for ; Sun, 25 Apr 2010 04:49:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=R+kzEQjNdUyHFLPQ+IlhuvVn9IsOihOkWRh+prF0Bzw=; b=ejXCLVL9kCAU2hyZVviBJf861CVdiFzXVQvgVFYn0x5AORN/xZdg+4zWAlNKswFDjM xxkPOgeubf5JPLhTq+dnBn5VAddFGAlFIwvvRcBjj9BymUKluYzYwJRaPITKIlCPy2Vn YjoUYapwuf6Q35YUhAz0l7q3sFMg+1y6o1rZQ= 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=C71md6tw0a2cY3qf519a7VYMxxWqMUlTF0X0ExlRkdNdRKK2NOHDWUSyUONK3Y8E+i /LkR8auF5eeJRmlpeBkOfmxZ6FEupoeVmv9Y6yEx1ZOkfn9x4L5VpzWDWEipfdm0YgDN 5lGRF8whV7Ixgpt6XhzU0cljnqKI7pjbuooWE= MIME-Version: 1.0 Received: by 10.229.213.208 with SMTP id gx16mr2910906qcb.35.1272196189275; Sun, 25 Apr 2010 04:49:49 -0700 (PDT) Received: by 10.229.89.147 with HTTP; Sun, 25 Apr 2010 04:49:49 -0700 (PDT) In-Reply-To: References: Date: Sun, 25 Apr 2010 17:19:49 +0530 Message-ID: Subject: Re: How to setup search engine for B2B web app From: Shalin Shekhar Mangar To: solr-user@lucene.apache.org Content-Type: multipart/alternative; boundary=0016361e898cf2480e04850e4131 --0016361e898cf2480e04850e4131 Content-Type: text/plain; charset=UTF-8 Hi Bill, On Sun, Apr 25, 2010 at 12:23 PM, Bill Paetzke wrote: > *Given:* > > - 1 database per client (business customer) > - 5000 clients > - Clients have between 2 to 2000 users (avg is ~100 users/client) > - 100k to 10 million records per database > - Users need to search those records often (it's the best way to navigate > their data) > > *The Question:* > > How would you setup Solr (or Lucene) search so that each client can only > search within its database? > > How would you setup the index(es)? > I'd look at setting up multiple cores for each client. You may need to setup slaves as well depending on search traffic. > Where do you store the index(es)? > Setting up 5K cores on one box will not work. So you will need to partition the clients into multiple boxes each having a subset of cores. > Would you need to add a filter to all search queries? > Nope, but you will need to send the query to the correct host (perhaps a mapping DB will help) > If a client cancelled, how would you delete their (part of the) index? > (this > may be trivial--not sure yet) > > With different cores for each client, this'd be pretty easy. -- Regards, Shalin Shekhar Mangar. --0016361e898cf2480e04850e4131--