I did observe the same..
1. updated an existing document.. means potentially marking the previous
document as "deleted" and adding a new version of it.. posted the JSON doc
using the Documents interface on the Admin UI.. left the default commit
within "1000" ms there on the Documents UI..
2. NOT optimized
3. Slave seems to be triggering the full replication (full index seems to be
replicated)
4. Using Solr 4.9
5. Does have the following on the master (but commit within from the
Documents UI might be overloading this.. (mentioning here just in case)
<autoCommit>
<maxDocs>100000</maxDocs>
<openSearcher>false</openSearcher>
</autoCommit>
Can someone look into this and suggest...
Thanks!
--
View this message in context:
http://lucene.472066.n3.nabble.com/SOLR-4-4-Slave-always-replicates-full-index-tp4113089p4148526.html
Sent from the Solr - User mailing list archive at Nabble.com.
