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 68EA518A19 for ; Wed, 23 Sep 2015 15:02:35 +0000 (UTC) Received: (qmail 33065 invoked by uid 500); 23 Sep 2015 15:02:31 -0000 Delivered-To: apmail-lucene-solr-user-archive@lucene.apache.org Received: (qmail 32986 invoked by uid 500); 23 Sep 2015 15:02:31 -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 32973 invoked by uid 99); 23 Sep 2015 15:02:31 -0000 Received: from Unknown (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 Sep 2015 15:02:31 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id A1EF1180ECD for ; Wed, 23 Sep 2015 15:02:30 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.879 X-Spam-Level: ** X-Spam-Status: No, score=2.879 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-us-west.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id 7HwT1GMeLBJw for ; Wed, 23 Sep 2015 15:02:29 +0000 (UTC) Received: from mail-ig0-f169.google.com (mail-ig0-f169.google.com [209.85.213.169]) by mx1-us-west.apache.org (ASF Mail Server at mx1-us-west.apache.org) with ESMTPS id 4985A20F60 for ; Wed, 23 Sep 2015 15:02:29 +0000 (UTC) Received: by igbkq10 with SMTP id kq10so120878843igb.0 for ; Wed, 23 Sep 2015 08:02:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=4+CDC94Xb/zCQI93xXSUizhRc+q9PzEWZE5X4H2zpGk=; b=I4ec0Xm7GbkLvxkBI4BoEC0A9ZklW8taoYID1YTO+I38BKCCkbH3AmVwL9ABOTBzlB 2SfflM51XMcb9DLwi/s8ZM27iamhE3cgZY0aRhPE97yrCEZJKZX3LcPaJ9D6WiQPkBoc fRXR8T8rqL6zrRpM45GYrb0g2j/YeTGnRqWohat7VGC298xTpKoaZF/gQWe9GF4LsvKj fEbkTGuk5rz2BU8rqGJUe3r6/ObrcnoKZbB/CykxBfQpnJZi0yjG8sVVSzdBsZEMSn0Y CqSV+wMB064qaEUZwN0dvZtdHICf0MtuBqEN7EZyUc6dUg8BYOwGstTFHCYDxGfzgiv9 mW4g== MIME-Version: 1.0 X-Received: by 10.50.45.106 with SMTP id l10mr22990373igm.57.1443020548586; Wed, 23 Sep 2015 08:02:28 -0700 (PDT) Received: by 10.107.9.93 with HTTP; Wed, 23 Sep 2015 08:02:28 -0700 (PDT) In-Reply-To: <5602BCA0.7020107@gmail.com> References: <5602B92D.50308@gmail.com> <5602BCA0.7020107@gmail.com> Date: Wed, 23 Sep 2015 08:02:28 -0700 Message-ID: Subject: Re: Sharing indexes From: Erick Erickson To: solr-user@lucene.apache.org Content-Type: multipart/alternative; boundary=089e0111b5e233e4a205206b67f6 --089e0111b5e233e4a205206b67f6 Content-Type: text/plain; charset=UTF-8 You should not be copying things into a Solr index unless 1> you absolutely and totally guarantee that no current Solr is running 2> you absolutely and totally guarantee that you replace it entirely You're really just asking for maintenance issues with this approach. I'd do one of two things: 1> ship your product with a pre-existing index that holds your documents or, preferably 2> use the MERGEINDEX core admin API command to get your required docs in the "live" index. <2> is robustly supported and has a far greater chance of not giving you grief. Best, Erick On Wed, Sep 23, 2015 at 7:52 AM, Henrique O. Santos wrote: > Hi Alessandro, > > The requirement is pretty simple. We have a product that makes use of Solr > collections. Anyone can download the product and deploy it locally > (alongside a local Solr instance) on their own machine and start using it. > To make it clear, each installation of the product operates by itself and > does not have knowledge of any other. It is meant to work on its own. > > For the product to work properly, the collections need to have some > starting documents there, like an admin user for instance in the user > collection. > > Thanks for the reply. > > > On 09/23/2015 10:44 AM, Alessandro Benedetti wrote: > >> Honestly is highly discouraged to share an index, making N Solr nodes >> using >> it. >> Can you express better your requirement ? Why can't you replicate the >> index ? >> >> Cheers >> >> 2015-09-23 15:37 GMT+01:00 Henrique O. Santos : >> >> Hello everyone, >>> >>> In our development efforts, we came into the necessity of sharing Solr >>> indexes with some initial documents to be deployed alongside our >>> application. For that, I just started copying the collection directory >>> with >>> its conf and data subdirs. >>> >>> That worked for some time, but it now I am getting some random errors. >>> One >>> of them says: >>> "SolrIndexWriter was not closed prior to finalize(), indicates a bug -- >>> POSSIBLE RESOURCE LEAK!!!" >>> >>> and the other: >>> "Error creating core [users]: Error opening new searcher" >>> >>> Errors show up when starting up Solr. And after multiples restarts, >>> eventually the cores start. >>> >>> So, is there any guidelines for sharing existing indexes? >>> >>> Thank you. >>> Henrique. >>> >>> >> >> > --089e0111b5e233e4a205206b67f6--