Hello (once more),
the problem could be fixed by doing the following:
BlockMgrJournal: Add "blockMgr.sync();" to sync()
NodeTableTrans: Add "base.sync();" to sync()
Yet, I don't know what side effects this would have. Could some of the
tdb specialists judge these changes?
Best wishes
André
On 06.11.2012 08:52, "Dr. André Lanka" wrote:
Hello TDB developers
thanks for you great work :)
Unfortunately, I encountered some problems while testing TDB 0.9.3. It
turned out that a dataset.commit() doesn't force NodeTableNative to
write the whole data to disk or that NodeTableNative.syncNeeded wasn't
set properly earlier.
By this, tdb stores can get broken even if no write transaction is
active if the jvm crashes. (The other files seem to be written fine, but
nodes.dat misses some information)
Is there a simple work-around for this problem (Simpler than patching
NodeTableNative)? Closing the store would help but is not feasible for us.
Thanks in advance
André
--
Dr. André Lanka * 0178 / 134 44 47 * http://dr-lanka.de
