Closed GoogleCodeExporter closed 9 years ago
Original comment by rarich...@gmail.com
on 7 Dec 2011 at 11:09
This has been started, will do more testing tomorrow on the soft failover. In
the event of being a corrupt database we move it aside. Failure to move it
aside and/or create the new database, or any other error results in history
being disabled.
Original comment by dan...@growl.info
on 1 Feb 2012 at 8:53
Added an attempt, after all attempts at making an on disk store have failed, to
create an in memory store, strictly for the purposes of the rollup. If it
can't create an in memory store, something has gone horribly wrong and we alert
the user, and we will exit(-1) upon return from the alert.
This could probably still use some improvement, particularly in preventing
more permanent history when using the in memory store, as it will balloon
memory usage. However, we warn the user about this, so for the time being,
marking as FixedInSource
relevant commits in Default in the dev repo:
[acd6c91d742e] - Initial work
[f576a9f68fa5] - In Memory store creation
Original comment by dan...@growl.info
on 1 Feb 2012 at 3:10
Original comment by dan...@growl.info
on 1 Feb 2012 at 3:11
Original comment by ch...@growl.info
on 11 Jan 2013 at 6:36
Original issue reported on code.google.com by
sigma...@gmail.com
on 1 Dec 2011 at 4:01