[
https://issues.apache.org/jira/browse/SOLR-4661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13620073#comment-13620073
]
Hoss Man commented on SOLR-4661:
--------------------------------
Aditya: in your thread on the solr-user@lucene list, you posted some other
examples of the generation being higher on the slave then on the master, and
you also posted some short log files from both your master & slave, but the log
files you posted don't seem to directly correspond to the snippets you posted
from requesting /replication?command=details in any of your mails or in this
issue (the generation numbers logged by SnapPuller on the slave don't match up)
Can you please attach a zip file containing a single cohesive example of:
* a master solrconfig.xml
* a slave solrconfig.xml (if different)
* the log files for both the master and slave from JVM startup to jvm shutdown
* any number of files containing the full response of getting the replication
details form the master & slave _with_ the timestamp of when these files were
generated.
The timestamps being crucial to helping us stitch together where in the flow of
log messages you are seeing this inconsistency.
If you are using bash, running two commands like this (one for master and one
for slave) while solr is running should be suitable...
{noformat}
while true; do date --utc && curl -sS
"http://localhost:8983/solr/collection1/replication?command=details&indent=truewt=json";
&& echo && echo && sleep 2; done 2>&1 > slave_rep_details.txt
{noformat}
> 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 7.1.1, JDK 1.7
> Reporter: Aditya
> Labels: gui, replication, web
> Attachments: IndexVersionSyncIssue.jpg
>
>
> 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.
> <response>
> <lst name="responseHeader">
> <int name="status">0</int>
> <int name="QTime">1</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">{color:red}1364835609803{color}</long>
> <long name="generation">{color:red}34{color}</long>
> <arr name="filelist">...</arr>
> </lst>
> </arr>
> <str name="isMaster">true</str>
> <str name="isSlave">false</str>
> <long name="indexVersion">{color:red}1364778010902{color}</long>
> <long name="generation">{color:red}31{color}</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">34</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: [email protected]
For additional commands, e-mail: [email protected]
