[ 
https://issues.apache.org/jira/browse/SOLR-4661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aditya updated SOLR-4661:
-------------------------

    Description: 
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 where i see two different Version Gen and 
version numbers. This creates confusion of having version out of sync, though 
its not. 


<response>
<lst name="responseHeader">
<int name="status">0</int>
<int name="QTime">2</int>
</lst>
<lst name="details">
<str name="indexSize">1.52 GB</str>
<str name="indexPath">/storage/solrdata/index/</str>
<arr name="commits">
<lst>
<long name="indexVersion">1364833076286</long>
<long name="generation">33</long>
<arr name="filelist">...</arr>
</lst>
</arr>
<str name="isMaster">true</str>
<str name="isSlave">false</str>
<long name="indexVersion">1364778010902</long>
<long name="generation">31</long>
<lst name="master">
<str name="confFiles">schema.xml</str>
<arr name="replicateAfter">
<str>commit</str>
<str>startup</str>
</arr>
<str name="replicationEnabled">true</str>
<long name="replicatableGeneration">33</long>
</lst>
</lst>
<str name="WARNING">
This response format is experimental. It is likely to change in the future.
</str>
</response>

  was:
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 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 where i see two different Version Gen and 
version numbers. This creates confusion of having version out of sync, though 
its not. 


<response>
<lst name="responseHeader">
<int name="status">0</int>
<int name="QTime">2</int>
</lst>
<lst name="details">
<str name="indexSize">1.52 GB</str>
<str name="indexPath">/storage/solrdata/index/</str>
<arr name="commits">
<lst>
<long name="indexVersion">1364833076286</long>
<long name="generation">33</long>
<arr name="filelist">...</arr>
</lst>
</arr>
<str name="isMaster">true</str>
<str name="isSlave">false</str>
<long name="indexVersion">1364778010902</long>
<long name="generation">31</long>
<lst name="master">
<str name="confFiles">schema.xml</str>
<arr name="replicateAfter">
<str>commit</str>
<str>startup</str>
</arr>
<str name="replicationEnabled">true</str>
<long name="replicatableGeneration">33</long>
</lst>
</lst>
<str name="WARNING">
This response format is experimental. It is likely to change in the future.
</str>
</response>

    
> Index Version & Gen Number out of sync on Admin UI
> --------------------------------------------------
>
>                 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 5.1
>            Reporter: Aditya
>              Labels: gui, replication, web
>
> 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 where i see two different Version Gen and 
> version numbers. This creates confusion of having version out of sync, though 
> its not. 
> <response>
> <lst name="responseHeader">
> <int name="status">0</int>
> <int name="QTime">2</int>
> </lst>
> <lst name="details">
> <str name="indexSize">1.52 GB</str>
> <str name="indexPath">/storage/solrdata/index/</str>
> <arr name="commits">
> <lst>
> <long name="indexVersion">1364833076286</long>
> <long name="generation">33</long>
> <arr name="filelist">...</arr>
> </lst>
> </arr>
> <str name="isMaster">true</str>
> <str name="isSlave">false</str>
> <long name="indexVersion">1364778010902</long>
> <long name="generation">31</long>
> <lst name="master">
> <str name="confFiles">schema.xml</str>
> <arr name="replicateAfter">
> <str>commit</str>
> <str>startup</str>
> </arr>
> <str name="replicationEnabled">true</str>
> <long name="replicatableGeneration">33</long>
> </lst>
> </lst>
> <str name="WARNING">
> This response format is experimental. It is likely to change in the future.
> </str>
> </response>

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

Reply via email to