
On 2/11/13 4:54 AM, Brandon Jackson wrote:
So it is a statistic that does not necessarily mean there is data corruption? Yes, but if your statistics grow with each server restart, you should consider a severely corrupted database. This could be caused by hardware failures, OOM OS exception handling, software bugs,...
Sent from my iPhone
On Feb 10, 2013, at 12:03 PM, Fabian Groffen
wrote: My questions are simple:
what causes crashes? The mserver5 (monetdb database) terminates in such a way that it can not be considered a clean shutdown, this is usually the case when the
On 10-02-2013 09:44:09 -0800, Tapomay Dey wrote: program gets terminated due to a condition that makes further execution impossible, e.g. memory faults. These are almost always program errors.
what is health? Health is the percentage of start-stop sequences compared to the number of times the database was actually started. E.g. how many times a start was followed by a clean shutdown (hence no crash).
how do we stop health from degrading? You can't, a database that crashes, and keeps on doing so will cause the health of the database to degrade.
Following is the status of my db- start count: 140 stop count: 1 crash count: 138 So, essentially, every time you start your database, it never reaches a point where you stop it cleanly, but instead your database crashes all the time.
-- Fabian Groffen fabian@monetdb.org column-store pioneer http://www.monetdb.org/Home _______________________________________________ users-list mailing list users-list@monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list
users-list mailing list users-list@monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list