Uploaded image for project: 'Solr'
  1. Solr
  2. SOLR-4661

Index Version & Gen look out of sync in replication UI when master searcher uses older commit then what is replicatable




      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..

      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.



        1. SOLR-4661.patch
          14 kB
          Stefan Matheis
        2. SOLR-4661.patch
          9 kB
          Chris M. Hostetter
        3. SOLR-4661.patch
          8 kB
          Chris M. Hostetter
        4. hoss_test.zip
          342 kB
          Chris M. Hostetter
        5. IndexVersionSyncIssue.jpg
          41 kB

        Issue Links



              hossman Chris M. Hostetter
              abakle Aditya
              0 Vote for this issue
              6 Start watching this issue