Currently, the page you referenced here:
http://wiki.apache.org/solr/SolrReplication
is the standard way to replicate incremental indexes.
You say your "worried about the extra http". Why?
Do you have any evidence that this would be a problem?
Http isn't inherently inefficient at all, and even if it was,
the slave asking occasionally if the master's index has
changed (say once every 5-10 minutes) isn't a worry.
The actual replication itself isn't costly protocol-wise.
So, just try it. Coming up in Solr 4.0 is "distributed indexing"
which is a whole different approach, but it's not released yet.
Best
Erick
On Mon, Feb 27, 2012 at 2:36 PM, Neel <neelkant.potlap...@aspiresys.com> wrote:
> Hi,
>
> We are already using embedded solr in our application. In production we have
> 3 app servers and each app server has a copy of index of each type. These
> indexes built externally once in a week and replaced.
>
> We now want allow incremental indexing and auto update to other servers
> rather than building indexes externally and replacing.
>
> I see there are few old posts
> {http://wiki.apache.org/solr/SolrCollectionDistributionScripts,
> http://wiki.apache.org/solr/CollectionDistribution}that says about
> distribution using scripts and rsync. For me this solution looks difficult
> follow on.
>
> I see standalone solrs provides replication
> (http://wiki.apache.org/solr/SolrReplication) using http requests. I like
> this approach, but worried about additional http request from application to
> standalone solr server.
>
> I now want to enhance standalone solr server to use it in directely in my
> application by removing the ui stuff etc and also work replication
> automatically. Can you please provide guidence how this can be done.
>
> Thanks in advance,
> Neel
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/Modify-Standalone-solr-server-to-use-it-application-without-http-request-tp3781826p3781826.html
> Sent from the Solr - User mailing list archive at Nabble.com.
