I would like to have the ability to keep requests from being slowed from new document adds and commits by having a separate index that gets updated. Basically a read-only and an updatable index. After the update index has finished updating with new adds and commits, I'd like to switch the update to the "live" read-only. At the same time, it would be nice to have the old read-only index become "updated" with the now live read-only index before I start this update process again.
1. Index1 is live and read-only and doesn't get slowed by updates 2. Index2 is updated with Index1 and gets new adds and commits 3. Index2 gets cache warming 4. Index2 becomes the live index read-only index 5. Index1 gets synced with Index2 so that when these steps start again, the updating is happening on an updated index. I know that this is possible but can't find a simple tutorial on how to do this. By the way, I'm using SolrNet in a windows environment. Thanks, Mike
