We're setting up two collection aliases. One's a read alias, one's a write alias.
When we need to start over with a new collection, we create the collection alongside the original, and point the write alias at it. When indexing is done, we point the read alias at it. Then you can delete the old collection when you feel good about the new one. Obviously this means that none of your clients should point at the collection directly, but rather one of the aliases depending on whether they're reading or writing. HTH, Michael Della Bitta ------------------------------------------------ Appinions 18 East 41st Street, 2nd Floor New York, NY 10017-6271 www.appinions.com Where Influence Isn’t a Game On Mon, Apr 8, 2013 at 5:45 PM, Bill Au <bill.w...@gmail.com> wrote: > We are using SolrCloud for replication and dynamic scaling but not > distribution so we are only using a single shard. From time to time we > make changes to the index schema that requires rebuilding of the index. > > Should I treat the rebuilding as just any other index operation? It seems > to me it would be better if I can somehow take a node "offline" and rebuild > the index there, then put it back online and let the new index be > replicated from there. But I am not sure how to do the latter. > > Bill
