Home/ Questions/Q 8381811
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-09T16:46:48+00:00

I’m working on a Solr 3.6 with ASP.net MVC3 e-commerce project. I’ve an index

  • 0

I’m working on a Solr 3.6 with ASP.net MVC3 e-commerce project.

I’ve an index of appx. 1 lac products in Solr. There is some changes in requirements, and we need to rebuild the whole index. Whole indexing is taking almost 1 & half hour during which site needs to be down.

How can I rebuild the index and also keep the site live which serving contents from older index. What is best practices to reduce down time while rebuilding the whole index. I wish I can do it with 100% uptime.

Edit
I’m storing a several URLs into Solr data as stored field and hence, which are dynamically generated while adding data into Solr. If I deploy application on different sub domain like test.example.com then it takes wrong URL, wherein it will only work with example.com. So hosting an another application is not an option for me.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    You can leverage the concept of multiple cores in Solr and thereby have a live core that users are currently searching against and a standby core where you can make schema changes, re-index, etc. Then using the SWAP command you can switch the live and standby cores without any user downtime. The swap will be handled internally by Solr and your users will never notice a difference.

    • 0