admin index version not updating

[Nathan Moon <nm...@fold3.com>]

I have a setup with a master and single slave, using the collection distribution scripts.  I'm not sure if it's relevant, but I'm running multicore also.  I am on version 3.4.0 (we are upgrading from 1.3).

My understanding that the indexVersion (a number) reported by the stats page (admin/stats.jsp) is a timestamp that should correspond to the time of the latest snapshot.  At least that's how it has behaved on version 1.3.

When I install a new snapshot on the slave (snapinstaller), it does not report any errors, and the logs/snapshot.current is updated with the latest snapshot, but the admin/stats page still reports the old version.  Actually, the version number increases by 4 each time I install a new index, but doesn't update to anywhere near the time of the latest snapshot (it's a few days off at this point).

I have verified that the slave is actually running on the latest index by searching for something that only exists in the latest index.

Am I misunderstanding how to interpret the indexVersion, or is the latest snapshot not getting fully installed?

Thanks

Nathan

Re: admin index version not updating

[Chris Hostetter <ho...@fucit.org>]

: I have a setup with a master and single slave, using the collection 
: distribution scripts.  I'm not sure if it's relevant, but I'm running 
: multicore also.  I am on version 3.4.0 (we are upgrading from 1.3).
: 
: My understanding that the indexVersion (a number) reported by the stats 
: page (admin/stats.jsp) is a timestamp that should correspond to the time 
: of the latest snapshot.  At least that's how it has behaved on version 
: 1.3.
	...
: I have verified that the slave is actually running on the latest index 
: by searching for something that only exists in the latest index.

The only thing that matters is if the slaves report thta they are using 
the same version as the master. if they are, then you can be certain they 
are using hte same index.

There has never been any documentation/assumption that indexVersion will 
corrispond to the last modified time of an index/snapshot.  indexVersion 
is a low level Lucene concept which just indicates if/when an index has 
changed by the value increasing -- the value is initialized using a 
timestamp when the index is first created, but after that it just 
increases monotomicaly as the index is changed.

Note the docs for IndexReader.getCurrentVersion in Lucene 2.4 (which is 
what Solr 1.3 was using)...

 * Reads version number from segments files. The version number is
 * initialized with a timestamp and then increased by one for each change of
 * the index.

https://svn.apache.org/viewvc/lucene/java/branches/lucene_2_4/src/java/org/apache/lucene/index/IndexReader.java


-Hoss