Hi, My question is generally to understand how people are dealing with such situation to minimize production downtime. Any suggestion/advice are welcomed.
We have Solr 3.5 setup as master Slave. Our UI almost has 70% data fetched from Solr Slaves where as other 30% are for authentication and other validations where it needs to hit DB. Index size is 20GB, # docs is 20M+ We have version upgrade like every 3 month coz of new features. If we make any schema change for adding new fields or removing fields from Index or changing Analyzers, we need to rebuild the index. We follow below steps. 1. Pull up Maintenance Pages 2. Upgrade DB 3. Upgrade Solr Schema (Master) Replication is disabled. 4. Start Index Rebuild. (if step 3) 5. Upgrade UI code 6. Index build complete ? Start Replication 7. Verify UI and Drop Maintenance Pages. As # 4 takes couple of hours compared to all other steps which run within few minutes, we need to have down time for the duration of that. Our challenge is to reduce the downtime to least possible. Making UI compatible with old version is not always possible. Any suggestions/advice would be a great help. Let me know if more information is required. thanks Aditya -- View this message in context: http://lucene.472066.n3.nabble.com/Production-Release-process-with-Solr-3-5-implementation-tp4017679.html Sent from the Solr - User mailing list archive at Nabble.com.
