Hi Team,
We have below critical issue in our project. Please suggest how to fix this
issue.
Whenever indexing happening on master, slave replicating documents
partially. Due to this, search results on website are showing wrongly.
During indexing on master, I have observed below versions on master and
slave
MASTER
---------
Master (searching) version - 1
Master (Replicable) version - 2
SLAVE
-------
Master (searching) version - 1
Master (Replicable) version - 2
Slave (Searching) version - 2
Once indexing gets completed, versions on both master and slave are same as
3 and also data replicated completely to slave.
Below is replication cong used in master and slave
<requestHandler name="/replication" class="solr.ReplicationHandler" >
<lst name="master">
<str name="replicateAfter">commit</str>
<str name="replicateAfter">optimize</str>
<str name="backupAfter">commit</str>
<str name="confFiles">schema.xml</str>
<str name="commitReserveDuration">00:00:10</str>
</lst>
<int name="maxNumberOfBackups">2</int>
<lst name="invariants">
<str name="maxWriteMBPerSec">16</str>
</lst>
</requestHandler>
<requestHandler name="/replication" class="solr.ReplicationHandler" >
<lst name="slave">
<str
name="masterUrl">http://localhost:8983/solr/global_web_index/replication</str>
<str name="pollInterval">00:00:20</str>
</lst>
</requestHandler>
Can any one please advice how to solve this issue as this is creating
escalations on project.
NOTE: As of now, I am disabling replication on slave before indexing to
avoid this issue.
Thanks in advance!
Regards,
G. Naresh Kumar
--
View this message in context:
http://lucene.472066.n3.nabble.com/Slave-replicating-partially-before-write-operation-completes-on-master-tp4331453.html
Sent from the Solr - User mailing list archive at Nabble.com.
