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 718AEE321 for ; Wed, 19 Dec 2012 12:48:13 +0000 (UTC) Received: (qmail 31649 invoked by uid 500); 19 Dec 2012 12:48:10 -0000 Delivered-To: apmail-lucene-solr-user-archive@lucene.apache.org Received: (qmail 31584 invoked by uid 500); 19 Dec 2012 12:48:10 -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 31573 invoked by uid 99); 19 Dec 2012 12:48:09 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 19 Dec 2012 12:48:09 +0000 X-ASF-Spam-Status: No, hits=1.7 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of anirudha81@gmail.com designates 209.85.223.180 as permitted sender) Received: from [209.85.223.180] (HELO mail-ie0-f180.google.com) (209.85.223.180) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 19 Dec 2012 12:48:05 +0000 Received: by mail-ie0-f180.google.com with SMTP id c10so2676213ieb.11 for ; Wed, 19 Dec 2012 04:47:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=+18bjbIfsmwXzLUaW1OFEM1cY0XqUewaP/6OFR0JDHY=; b=aNU9Zrz+eBKzzgUCwzUjMuzxAMuEHQTJK0ALRPr14X2CZMGRo2iH1TyBcp70H53aeg WQ3h7fxiu7PFk1D51BwAobnKEOWvHyPdpZuAaifdxAQoCZVt6Wa4rjRNZnB4RVd2Tpkb 68W2df7jXy4c7tD88NUcaBsAWy03VlQYrZ2eXrlmtH7YKXu9maZZl+GT7UQJr2z5rzTM xNbN7FqYMToD2RShLzrA7Mo3pa4gP0nNLcTR3sR4bt5nnp0eLMNK9mlPCQAK+neNxV+q zQL/Y2xXfTGaCcr3h9JknRhOBCvmwWxzG6uhF91ecP+IuRv5GrxXzdlILrMs6wNivoLl IzUA== MIME-Version: 1.0 Received: by 10.50.106.227 with SMTP id gx3mr6931589igb.10.1355921264802; Wed, 19 Dec 2012 04:47:44 -0800 (PST) Sender: anirudha81@gmail.com Received: by 10.64.82.198 with HTTP; Wed, 19 Dec 2012 04:47:44 -0800 (PST) In-Reply-To: References: Date: Wed, 19 Dec 2012 07:47:44 -0500 X-Google-Sender-Auth: 7iEMI5YplXMdilPzhaXfrQoNO48 Message-ID: Subject: Re: Solr Cloud 4.0 Production Ready? From: Anirudha Jadhav To: "solr-user@lucene.apache.org" Content-Type: multipart/alternative; boundary=e89a8f2351af54fac604d134055e X-Virus-Checked: Checked by ClamAV on apache.org --e89a8f2351af54fac604d134055e Content-Type: text/plain; charset=UTF-8 I am curious to know what issues you are facing with 3.5 and large indices. We use 3.5 with 200g indices with no issues until now -Ani On Tuesday, December 18, 2012, Luis Cappa Banda wrote: > Any idea about when Solr 4.1 will be released? > > 2012/12/18 Otis Gospodnetic > > > > Hi, > > > > If you are not in a rush, I'd wait for Solr 4.1. Not that Solr 4.0 is > not > > usable, but Solr 4.1 will have a ton of fixes. > > > > Otis > > -- > > SOLR Performance Monitoring - http://sematext.com/spm/index.html > > Search Analytics - http://sematext.com/search-analytics/index.html > > > > > > > > > > On Tue, Dec 18, 2012 at 2:46 AM, Cool Techi > > > > wrote: > > > > > Hi, > > > > > > We have been using solr 3.5 in our production for sometime now and > facing > > > the problems faced by a large solr index. We wanted to migrate to Solr > > > Cloud and have started some experimentation. But in the mean time also > > > following the user forum and seem to be noticing a lot of bugs which > were > > > raised post the release and will be fixed in 4.1. > > > > > > Should we wait for 4.1 release for production or we can go ahead with > the > > > current release? > > > > > > Regards, > > > Ayush > > > > > > > > > > > > > > > -- > > - Luis Cappa > -- Anirudha P. Jadhav --e89a8f2351af54fac604d134055e--