couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sebastian Cohnen <sebastiancoh...@googlemail.com>
Subject Re: consistence? buffering?
Date Tue, 14 Sep 2010 15:59:00 GMT
Hi Wolfgang,

two ideas:
1) do you have delayed_commits = true;? In that case couchdb will not sync immediately to
disk which could result in data-loss,
2) you also experience some sort of browser-caching issue (in which case couchdb is not to
blame).

Best

Sebastian

On 14.09.2010, at 17:02, Wolfgang Egger wrote:

> Servus,
> 
> everywhere I read about couchdb i can read, that one benefit of couchdb would
> be, that the db is always in a consistant state. 
> This seems not to be true for
> couchdb 1.0 under ubuntu 10.4 called by firefix 3.5 and a couchapp-driven-app
> (myCouchApp).
> 
> The following behaviour I have seen more than one time.
> 
> 1) I develop some time and do some pushes while that. Everythig is nice,
> requesting myCouchApp shows the newest version.
> 2) I close the Laptop so the system is going to "sleep" and stored on the disk
> 3) I reopen the Laptop so the system wakes up und then, if I request myCouchApp,
> there is a very very old version served.
> 4) I push the last source again, shut down the couchapp and restart it and new
> version of my sources is running
> 
> It looks, like the pushes are buffered and the buffer will not be written to
> disk while closing the Laptop. Is that possible or what else may be the reason
> for this behaviour and how to prevent?
> 
> Have nice and relaxing day
> 
>   Wolfgang
> 
> 


Mime
View raw message