Return-Path: X-Original-To: apmail-lucene-solr-user-archive@minotaur.apache.org Delivered-To: apmail-lucene-solr-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 9DE5210A5A for ; Tue, 26 Nov 2013 07:46:26 +0000 (UTC) Received: (qmail 74079 invoked by uid 500); 26 Nov 2013 07:46:13 -0000 Delivered-To: apmail-lucene-solr-user-archive@lucene.apache.org Received: (qmail 73361 invoked by uid 500); 26 Nov 2013 07:46:08 -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 Delivered-To: moderator for solr-user@lucene.apache.org Received: (qmail 42782 invoked by uid 99); 26 Nov 2013 05:58:05 -0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy includes SPF record at spf.trusted-forwarder.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:content-type; bh=JaqiL99WhugeuUVZRxX2ht0ogr2TIltMyM0rP5+cEaY=; b=VxrJBxAf299vENgzPCcl8YatEDq6wMoxX0c2kYwD58OP0TbX67HpJl6CWWwfTMwT9x GwOWQxjiLEt4Us+YxxkOLVQ6aVWZnrFuR2U0r1G4tHJ22/qBeFXrRTdl2qFhbDaNG0cx C29Y5xJrYUw3m/E6F6g7zqHHuXXAkVd/mOfyVDRDDe3iqejABWsNpVmAZule7KIZcvaB kkGjJIkdBTR7ZutczUGTyd9wqJZLTc5g3TFvkN9jz3TPzQR9Np3/US3jT7a0jZjLGi5t iCebDxI9qxqsBrm7Wy+ESp73v93o+hAGrxZN87p/Q5jwlF9uDmMvNmuewTAZT4p21Xhr 6TNA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=JaqiL99WhugeuUVZRxX2ht0ogr2TIltMyM0rP5+cEaY=; b=aufUOwlOtgEUFTuwXgX8Ztj8hrLaa5AB/fPAx88+lCoRWEQ7BviZQH7nF4gItbA5Kx YwuVTQ+wlJa/GdS7NEAMfV5BX4lcwRYqQU/qhUaHXbu3awcvNU6jvaK9iw1WkUn4+B4p CNcRYjVkr6itgXAGEpgqhTGIZgMLVM7gDOSMegpqy8u5zJulV9YaKMg+118c0f2m8ysz rl+PGr1UeHtyhEMD/pUiIzmhkzDYyMD5dcijKoy2rvepxp0WmzKSDz955c0xHftn3DDX mHc64SpQ9AUz6ucfJwTy5pQjuUHPZ64TjLlW5HYyF8eG6GSL75DA7bZWe9k8gLYlhg0t 5PEQ== X-Gm-Message-State: ALoCoQljI/dZTxU92PICfaZ4AYpg/xZR5etlODFsxkakoxDUYr9JnXbXr4vskJBbjxCBXplIfU+/ MIME-Version: 1.0 X-Received: by 10.42.149.130 with SMTP id w2mr122923icv.64.1385445459409; Mon, 25 Nov 2013 21:57:39 -0800 (PST) Sender: sameer@sameermaggon.com X-Originating-IP: [209.116.67.22] In-Reply-To: <4E51E09EAD044A07BC914279DC729594@nclan.netcompany.dk> References: <3EF1345F50554F7088E5E15AE594D2D2@nclan.netcompany.dk> <4E51E09EAD044A07BC914279DC729594@nclan.netcompany.dk> Date: Mon, 25 Nov 2013 21:57:39 -0800 X-Google-Sender-Auth: UuTQoBzIt1-Aknx5e6s2ACF-6WI Message-ID: Subject: Re: New to Solr - Need advice on clustering From: Sameer Maggon To: solr-user@lucene.apache.org Content-Type: multipart/alternative; boundary=90e6ba1efbf076d96704ec0e2884 X-Virus-Checked: Checked by ClamAV on apache.org --90e6ba1efbf076d96704ec0e2884 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Anders, Take a look at Solr Replication. Essentially, you'll treat one as a master & one as a slave. Both master & slave can be used to serve traffic. If one of them goes down, the other can be used as a master for the interim. http://wiki.apache.org/solr/SolrReplication Sameer. -- http://measuredsearch.com On Mon, Nov 25, 2013 at 9:50 PM, Anders K=E5re Olsen wrote: > > Hi Gora > > Thank you for your reply. > > We are planning on having a loadbalancer in front of our frontend servers= . > > If I have two distinct solr indexes, how will I keep them synchronized? I > expect that one of the frontend servers will have the task of updating th= e > product repository on the e-commerce site. This server will then update t= he > local solr index after product update has finished. > > Is there an easy way that I can keep the two indexes synchronized withou= t > solrcloud? > > Regards > Anders > > -----Oprindelig meddelelse----- From: Gora Mohanty > Sent: Tuesday, November 26, 2013 2:37 AM > To: solr-user@lucene.apache.org > Subject: Re: New to Solr - Need advice on clustering > > > On 26 November 2013 01:44, Anders K=E5re Olsen wrote: > >> Hi Solr-users >> >> I=92m trying to setup Solr for search and indexing on the project I=92m >> working on. >> >> My project is a e-commerce B2B solution. We are planning on setting up 2 >> frontend servers for the website, and I was planning on installing Solr = on >> these servers. We are using Windows Server 2012 for the frontend servers= . >> >> We are not expecting a huge load on the servers, so we expect these 2 >> servers to be adequate to handle both the website and search index. >> >> I have been looking at SolrCloud and ZooKeeper. Howver I have read that >> you need at least 3 ZooKeepers in an ensamble, and I only have 2 servers= . >> >> I need to handle the situation where one of the servers crashes, so I >> need both servers to have a Solr index. >> > [...] > > If you do not want to get into SolrCloud, a simpler > solution might be a HTTP load balancer in front of > the two Solr instances. Hardware load balancers are > better, but more expensive. A software load balancer > like haproxy should meet your needs. > > Regards, > Gora > --90e6ba1efbf076d96704ec0e2884--