How are you committing? Are you committing every document? (you shouldn't).
Or, sin of all sins, are you _optimizing_ frequently? That'll cause your entire index to be replicated every time. Best, Erick On Thu, Jan 23, 2014 at 3:26 PM, sureshrk19 <sureshr...@gmail.com> wrote: > Hi, > > I have configured single core master, slave nodes on 2 different machines. > The replication configuration is fine and it is working but, what I observed > is, on every change to master index full replication is being triggered on > slave. > I was planning to get only incremental indexing done on every change. > > *Master config:* > > <requestHandler name="/replication" class="solr.ReplicationHandler"> > <lst name="master"> > <str name="replicateAfter">startup</str> > <str name="replicateAfter">commit</str> > <str name="confFiles">schema.xml,stopwords.txt,elevate.xml</str> > <str name="commitReserveDuration">00:00:20</str> > </lst> > <str name="maxNumberOfBackups">1</str> > </requestHandler> > > *Slave config:* > > <requestHandler name="/replication" class="solr.ReplicationHandler" > > <lst name="slave"> > <str name="masterUrl">http://<IP>:<Port>/solr/core0/replication</str> > <str name="pollInterval">00:00:20</str> > </lst> > </requestHandler> > > > What I observed is, the index directory name is appended with timestamp > i.e., /index.<timestamp>/ on slave instance. > > I have seen a similar issue on older version of SOLR and it is fixed in 4.2 > (per description). So, not sure if this is related to the same. > > https://issues.apache.org/jira/browse/SOLR-4471 > http://lucene.472066.n3.nabble.com/Slaves-always-replicate-entire-index-amp-Index-versions-td4041256.html#a4041808 > > > Any pointers would be highly appreciated. > > Thanks, > Suresh > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/SOLR-4-4-Slave-always-replicates-full-index-tp4113089.html > Sent from the Solr - User mailing list archive at Nabble.com.
