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 A8CCEDF44 for ; Wed, 15 May 2013 21:57:38 +0000 (UTC) Received: (qmail 17637 invoked by uid 500); 15 May 2013 21:57:26 -0000 Delivered-To: apmail-lucene-solr-user-archive@lucene.apache.org Received: (qmail 17574 invoked by uid 500); 15 May 2013 21:57:26 -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 17553 invoked by uid 99); 15 May 2013 21:57:26 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 15 May 2013 21:57:26 +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 (nike.apache.org: domain of shreejayn@gmail.com designates 209.85.223.178 as permitted sender) Received: from [209.85.223.178] (HELO mail-ie0-f178.google.com) (209.85.223.178) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 15 May 2013 21:57:20 +0000 Received: by mail-ie0-f178.google.com with SMTP id b11so4751471iee.23 for ; Wed, 15 May 2013 14:56:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=Bkc3kEgoV/3tknsgY5AWYO7nBIwU+VkOkdsOVy0TCiU=; b=hk/sXuC6seoo6nwSa3tcXQNZ3T6gDpGFxUMBLEXN8s2KFNno3uggsYFA8j8DUg7BKT sQN2J2capY3ZNmmYFQGA9O7t3zaW9TJWtLhXQvE60rNK+l0oU60nx2TO9fVyQmtL5nT7 GIPweow2cw+Kg26mqZtX13EQDju8+ARwQmZdotnAlu62xE0n2uBS4tol8cnabAtNuYZT S1xs5GRiono+7sLIvNB6QHn9H7RkxjAdKqsgST967SEO3I4f7jZt+yzn2sWNUT70aTxI g1dwe6Nj5iJBbnZJGPiCyzW2JyVaKRcijZfJEXnq8vHQMh8gky0vNkYe/y1u5KHTJADC Fw+w== MIME-Version: 1.0 X-Received: by 10.50.73.165 with SMTP id m5mr6703858igv.28.1368655019548; Wed, 15 May 2013 14:56:59 -0700 (PDT) Received: by 10.64.76.198 with HTTP; Wed, 15 May 2013 14:56:59 -0700 (PDT) In-Reply-To: <5193E669.7040506@jhu.edu> References: <5193E669.7040506@jhu.edu> Date: Wed, 15 May 2013 14:56:59 -0700 Message-ID: Subject: Re: replication without automated polling, just manual trigger? From: Shreejay Nair To: solr-user@lucene.apache.org Content-Type: multipart/alternative; boundary=089e013a203042a7d204dcc8d401 X-Virus-Checked: Checked by ClamAV on apache.org --089e013a203042a7d204dcc8d401 Content-Type: text/plain; charset=ISO-8859-1 You can disable polling so that the slave never polls the Master(In Solr 4.3 you can disable it from the Admin interface). . And you can trigger a replication using the HTTP API http://wiki.apache.org/solr/SolrReplication#HTTP_API or again, use the Admin interface to trigger a manual replication. On Wed, May 15, 2013 at 12:47 PM, Jonathan Rochkind wrote: > I want to set up Solr replication between a master and slave, where no > automatic polling every X minutes happens, instead the slave only > replicates on command. [1] > > So the basic question is: What's the best way to do that? But I'll provide > what I've been doing etc., for anyone interested. > > Until recently, my appliation was running on Solr 1.4. I had a setup that > was working to accomplish this in Solr 1.4, but as I work on moving it to > Solr 4.3, it's unclear to me if it can/will work the same way. > > In Solr 1.4, on slave, I supplied a masterUrl, but did NOT supply any > pollInterval at all on slave. I did NOT supply an "enable" > "false" in slave, because I think that would have prevented even manual > replication. > > This seemed to result in the slave never polling, although I'm not sure if > that was just an accident of Solr implementation or not. Can anyone say if > the same thing would happen in Solr 4.3? If I look at the admin screen for > my slave set up this way in Solr 4.3, it does say "polling enabled", but I > realize that doesn't neccesarily mean any polling will take place, since > I've set no pollInterval. > > In Solr 1.4 under this setup, I could go to the slave's admin/replication, > and there was a "replicate now" button that I could use for manually > triggered replication. This button seems to no longer be there in 4.3 > replication admin screen, although I suppose I could still, somewhat less > conveniently, issue a `replication?command=**fetchindex` to the slave, to > manually trigger a replication? > > > > Thanks for any advice or ideas. > > > > [1]: Why, you ask? The master is actually my 'indexing' server. Due to > business needs, indexing only happens in bulk/mass indexing, and only > happens periodically -- sometimes nightly, sometimes less. So I index on > master, at a periodic schedule, and then when indexing is complete and > verified, tell slave to replicate. I don't want slave accidentally > replicating in the middle of the bulk indexing process either, when the > index might be in an unfinished state. > --089e013a203042a7d204dcc8d401--