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
