[
https://issues.apache.org/jira/browse/SOLR-4661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13634041#comment-13634041
]
Joel Bernstein commented on SOLR-4661:
--------------------------------------
I'm concerned about the empty commits opening a new index searcher on the
slave. In my testing I found that empty commits do not cause a new searcher to
open on master, but do open a new searcher on the slave. This feels like a bug.
I'll investigate further. Wondering what peoples thoughts are on this?
> Index Version & Gen look out of sync in replication UI when master searcher
> uses older commit then what is replicatable
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: SOLR-4661
> URL: https://issues.apache.org/jira/browse/SOLR-4661
> Project: Solr
> Issue Type: Bug
> Components: replication (java), web gui
> Affects Versions: 4.2
> Environment: Solr 4.2 on Linux with JBoss 7.1.1, JDK 1.7
> Reporter: Aditya
> Labels: gui, replication, web
> Attachments: hoss_test.zip, IndexVersionSyncIssue.jpg,
> SOLR-4661.patch, SOLR-4661.patch, SOLR-4661.patch
>
>
> the ReplicationHandler (and the replication admin UI screen) report the index
> version & gen for the master based on what commit point is currently open for
> searching -- but this is not necessarily the most recent commit point
> available for replication.
> Thus, it can appear that a slave has "gotten ahead" of the master, if there
> are "empty commits" (because of reader reopening shotcuts) or commits using
> openSearcher=false.
> We need to add additional data to help make it clear there is no actual
> problem in this sitation.
> Summary of original bug report..
> {panel}
> Index and Gen number on Slave is higher than master.
> If you apply commit on master with no pending docs then the commit time stamp
> and gen is incremented. When Slaves polls master for replication it see the
> index version difference and starts replicating but all files are skipped.
> On Admin UI (on Slaves) the version number displayed for master is old where
> as for slave is the latest which is higher than master.
> Below is the response from master (/replication?command=details) where i see
> two different Version an Gen numbers. This creates confusion of having
> version out of sync, though its not.
> ...
> {panel}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
