Hi, After reading your use case I would consider using stale=false. It's a synchronous call that takes a little while longer, but the performance hit on the cluster shouldn't be that bad. Of course this depends on how often you call the view.
You mentioned that it's important that a city is included in the view right after inserting it. This sounds like the view is requested by a user who just inserted a city. If other users requested the view, would it be a problem if they didn't see the city until a few seconds later? If not you could even consider adding the just-added city manually in the view results, if it's not there already, and then not using stale=false. Managing big data systems is a matter of embracing and designing for stale data. I hope this helps. 2014-03-27 22:36 GMT+01:00 Jason Fill <[email protected]>: > Lasse, > > I was interested in what you came up with here. We are in a situation > where we really need to be able to read the updated data from the views > almost instantly and are trying to figure out best practices. I posted > more details over on the Couchbase site ( > http://www.couchbase.com/communities/q-and-a/getting-most-updatedreliable-data-back-view) > on some options we are considering - but really curious to see how you > handled it. > > Any info you (or anyone) can provide would be greatly appreciated. > > Thanks, > > Jason > > On Thursday, May 2, 2013 5:05:10 AM UTC-5, Lasse Schou wrote: >> >> I'm testing Couchbase Server 2.0 for a use case that heavily depends on >> the views, and in particular the freshness of the views. I've been >> experimenting with the updateInterval and updateMinChanges parameters. It >> wasn't clear from the docs whether ANY of the two criteria had to be met >> before the view update daemon would trigger an update, or BOTH of the >> criteria. Couchbase replied that the update daemon triggers updates when >> the first of the two criteria is met (every X seconds OR after Y document >> changes). >> >> However that's not the behavior I see. I can make the updateMinChanges >> work fine, but the updateInterval parameter doesn't seem to have any >> effect. The views aren't updated automatically. >> >> Have you seen this before? And do you know how to check the status of the >> daemon, and perhaps the logs? >> >> Thanks, >> >> Lasse Schou >> > -- > You received this message because you are subscribed to the Google Groups > "Couchbase" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Couchbase" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
