I'm talking about an update request. So if you make an update, when it returns, your next search will see the update, because it will be on all replicas. Another process that is searching rapidly may see an "eventually" consistent view though (very briefly). We have some ideas to make that view "more consistent", for example by allowing for searcher leases.
- Mark On Thu, Nov 15, 2012 at 8:53 AM, Bill Au <bill.w...@gmail.com> wrote: > Thanks for the info, Mark. By "a request won't return until it's affected > all replicas", are you referring to the update request or the query? > > Bill > > > On Wed, Nov 14, 2012 at 7:57 PM, Mark Miller <markrmil...@gmail.com> wrote: > >> It's included as soon as it has been indexed - though a request won't >> return until it's affected all replicas. Low latency eventual consistency. >> >> - Mark >> >> On Nov 14, 2012, at 5:47 PM, Bill Au <bill.w...@gmail.com> wrote: >> >> > Will a newly indexed document included in search result in the shard >> leader >> > as soon as it has been indexed locally or is it included in search result >> > only after it has been forwarded to and indexed in all the replicas? >> > >> > Bill >> >> -- - Mark
