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 52DCDD0B6 for ; Tue, 18 Dec 2012 07:47:12 +0000 (UTC) Received: (qmail 35243 invoked by uid 500); 18 Dec 2012 07:47:09 -0000 Delivered-To: apmail-lucene-solr-user-archive@lucene.apache.org Received: (qmail 35190 invoked by uid 500); 18 Dec 2012 07:47: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 Received: (qmail 35158 invoked by uid 99); 18 Dec 2012 07:47:07 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 Dec 2012 07:47:07 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of cooltechie@outlook.com designates 65.55.111.174 as permitted sender) Received: from [65.55.111.174] (HELO blu0-omc4-s35.blu0.hotmail.com) (65.55.111.174) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 Dec 2012 07:46:58 +0000 Received: from BLU002-W150 ([65.55.111.136]) by blu0-omc4-s35.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Mon, 17 Dec 2012 23:46:37 -0800 X-EIP: [VJpu60mcvzgA2z+jAPtAtF8Qf1rA0bXG] X-Originating-Email: [cooltechie@outlook.com] Message-ID: Content-Type: multipart/alternative; boundary="_a6ce21ab-30e6-4066-a617-f28f9ea1f608_" From: Cool Techi To: "solr-user@lucene.apache.org" Subject: Solr Cloud 4.0 Production Ready? Date: Tue, 18 Dec 2012 13:16:37 +0530 Importance: Normal MIME-Version: 1.0 X-OriginalArrivalTime: 18 Dec 2012 07:46:37.0763 (UTC) FILETIME=[CF5B1930:01CDDCF3] X-Virus-Checked: Checked by ClamAV on apache.org --_a6ce21ab-30e6-4066-a617-f28f9ea1f608_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi=2C We have been using solr 3.5 in our production for sometime now and facing t= he 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 pos= t 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 c= urrent release? Regards=2C Ayush = --_a6ce21ab-30e6-4066-a617-f28f9ea1f608_--