Hi all,
we're about to implement a project that uses H2 on board of some RFID
readers, for a steel factory. The database will be used to store RFID
readings, so we will write few datas relatively often (2 records/second,
maybe).
Problem is, being an "embedded" scenario, the readers will usually go down
without a proper, clean shutdown, at a frequency of 3-4 times per day.
There's really no way to avoid the possibility that the power-off happens
during a write.
OS is Linux, with a proper journaled filesystem (EXT4) stored on a micro-sd
card; CPU is an Atom processor. Supplier assures me that as far as the
operating system is concerned, this scenario is O.K.
Which is the best way to avoid corruptions of H2, detect them and recover
from them, in a programmatical way? No user interaction should be required.
In particular:
- Which url parameters should we use? is LOG=2 enough?
- Which version should we use? 172, nightly, wait for the next one? Project
will be rolled out at 20 of july.
- Will it make any difference if I create indexes? Does them increase the
"exposed area" for corruptions?
- Which is the worst-case scenario for this? I'm ok losing the last few
writes.
Thanks a lot,
Germano
--
You received this message because you are subscribed to the Google Groups "H2
Database" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/h2-database.
For more options, visit https://groups.google.com/groups/opt_out.
