On 2/6/08, Ted Dunning <[EMAIL PROTECTED]> wrote: > Our best work-around is to simply take a shard out of service during delivery > of an updated index. This is obviously not a good solution.
How many shard servers are serving each shard? If it's more than one, you can have the rest of the shard servers sharing the query workload while one shard server loads a new version of a shard. We'd like to start an open source project for this (or join if one already exists) if there is enough interest.
