On Wed, Aug 24, 2011 at 20:30, Jason Smith <[email protected]> wrote:
> On Thu, Aug 25, 2011 at 9:55 AM, Paul Davis <[email protected]> > wrote: > >> 1. CouchDB has an odd, idiosyncratic, feature where GET queries > >> produce side-effects. From HTTP, there are no side-effects, but as you > >> can see, GETting a view can spawn couches processes and write files to > >> the disk. Perhaps you could add ?stale=ok to all of your queries used > >> in production. To my knowledge, stale=ok guarantees that couchjs will > >> not be involved in servicing that query. This protects your users from > >> seeing map/reduce errors. The down-side is that you must of course > >> query the views yourself to keep them current. > As of CouchDB 1.1 you may use ?stale=update_after to trigger background rebuilding but instantly stale data if the view is out of date.
