If it helps, these are filelist output before and after restarting master on
a sample setup:
Before restarting master:
---------------------------
{indexSize=113.82 KB,
indexPath=C:\JavaStuff\Solr\replication\solrhome\master\data\index,
commits=[{indexVersion=1252480003511,generation=107,filelist=[_35.fdx,
_35.frq, _35.tii, _35.fdt, _35.tis, segments_2z, _35.fnm,
_35.prx]}]
,isMaster=true,isSlave=false,indexVersion=1252480003511,generation=107}
http://localhost:8081/master/replication
Poll Interval null
Local Index Index Version: 1252480003511, Generation: 107
Location: C:\JavaStuff\Solr\replication\solrhome\repeater\data\index
Size: 57.29 KB
Config Files To Replicate: schema.xml,stopwords.txt,synonyms.txt
Trigger Replication On: [optimize, startup]
Times Replicated Since Startup: 25
Previous Replication Done At: Wed May 04 10:51:01 EST 2011
Config Files Replicated At: null
Config Files Replicated: null
Times Config Files Replicated Since Startup: null
After restarting master:
---------------------------
{indexSize=113.82 KB,
indexPath=C:\JavaStuff\Solr\replication\solrhome\master\data\index,
commits=[],
isMaster=true,isSlave=false,indexVersion=1252480003512,generation=108}
Master http://localhost:8081/master/replication
Poll Interval null
Local Index Index Version: 1252480003511, Generation: 107
Location: C:\JavaStuff\Solr\replication\solrhome\repeater\data\index
Size: 57.29 KB
Config Files To Replicate: schema.xml,stopwords.txt,synonyms.txt
Trigger Replication On: [optimize, startup]
Times Replicated Since Startup: 25
Previous Replication Done At: Wed May 04 10:51:01 EST 2011
Config Files Replicated At: null
Config Files Replicated: null
Times Config Files Replicated Since Startup: null
Hope someone would be able to help.
Thanks
On Wed, May 4, 2011 at 3:46 PM, Maduranga Kannangara <madura...@gmail.com>wrote:
> Hi All,
>
> We use Solr 1.4.1. Single core setup with a repeater (for QA) and a few
> slaves (for Production).
>
> Master will index many sources and make data ready. Once all data is
> "ready-for-production", optimization will take place. On master
> "replicateAfter" is set to "optimize". (Subsequently on repeater
> replicateAfter=commit,startup). We do not want to use
> replicateAfter=startup,optimize on master as that would release bad data. As
> you can see, a bunch of sources should fit together to be able to release a
> sensible product. So we use "replicateAfter=optimize" to denote data is now
> okay to move to the next level.
>
> The problem is when master is restarted the filelist command on
> ReplicationHandler returns nothing and replication will not take place until
> another optimise command is done to master.
>
> How can I preserve the "optimized" state (or filelist or commit-points, not
> sure what keyword to use..) even after a master restart so that slaves can
> carry on from there. (I saw the mail thread Yonik has answered:
> "Replication filelist command failure on container restart", but I am trying
> to figure out if its possible to persist this file-list or
> indexDeletionPolicy or whatever that state -- please correct me on that
> and sorry for my layman language)
>
> We have too many master indexes setup in this way, therefore its not a good
> idea for us to run optimize or have replicateAfter=startup on each index as
> that will reduce the data quality or possible level-of-automation.
>
> Any solution to work around or fix this issue is highly appreciated.
>
> Thanks in advance
> Madu
>
>
>
