Thanks Paul, In our case we need to upgrade DB with new version before re-building the index as we pull data from DB. Once DB is upgraded, UI needs to be upgraded too.
We do the same in case when there is no DB schema changes. We disable the replication and build index on Master. Once index is ready we upgrade UI, enable replication, verify Ui and drop maintenance page. This is like doing the background indexing. But when we have Schema update for both DB and Solr, this is where we run into longer downtime. -- View this message in context: http://lucene.472066.n3.nabble.com/Production-Release-process-with-Solr-3-5-implementation-tp4017679p4017693.html Sent from the Solr - User mailing list archive at Nabble.com.
