Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: solr-user@lucene.apache.org
Received-SPF: pass (athena.apache.org: domain of jordanmendler@gmail.com
 designates 209.85.200.170 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:sender:from:date:x-google-sender-auth:message-id
         :subject:to:content-type;
        b=wmwgpGat4bW9BPGsi11h3wrrysMI4U9V2sE7Saz3keakLr52aRSakccXKnxtvYE2BF
         m5ItOK5wnZMlLTohjGIenXt6s4Fy+PTuHGe9wUzHiQ4pqZVVJ8XN9x33yJXbb7yfZ/Fe
         EqARaQaqvvEUJ/jUThelPY+mRAfHuwvKg4YZo=
MIME-Version: 1.0
Sender: jordanmendler@gmail.com
From: Jordan Mendler <jmendler@ucla.edu>
Date: Sun, 12 Jul 2009 14:48:53 -0700
Message-ID: <654e62180907121448h51c8de75u320869b7349ccef2@mail.gmail.com>
Subject: Replication on Slave startup (Solr 1.4)
To: solr-user@lucene.apache.org
Content-Type: multipart/alternative; boundary=00504502cb6c1b892b046e892ddf

--00504502cb6c1b892b046e892ddf
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Hi all,

I am having an issue where Solr slaves do not pull replication data on
startup. Rather they wait until the amount of time of poll_interval, before
pulling the initial index. This is causing new and rebooted nodes to have a
stale index for polling_interval seconds, in addition to the amount of time
it takes to pull the data.

Is there some native setting to make slaves pull on startup? A hack could be
to add a curl *http://localhost:solr_port
/solr/replication?command=fetchindex* to my Solr startup script, but this
does not seem like a clean way to do it.

Furthermore, has anyone tried to 'warm' nodes after provisioning before
bringing them into a production read cluster? I would be curious what
procedure you are using to pull and warm the new index from the mastern
before exposing newly provisioned slaves to your production load balancer.

Thanks so much,
Jordan

--00504502cb6c1b892b046e892ddf--