Hi Christian,
Let's return with this discussion to the mailing list as I think this might be interesting for everybody.
Summary: I had stability problems. In my tests, once BaseX reached certain size It would start throwing exceptions with stacktraces reaching deep into the low-level classes that shuffle the bits and bytes on disk.
I now started a test run of our system with PARALLEL=1 and UPDINDEX=false. The system has been running without any exceptions for 17 hours. Starting with an empty data there have been almost 200K queries and commands. This is a record.
Now, what exactly are the consequences of UPDINDEX being false.
Can I do queries? What kind of queries I can't do? What kind of queries will be slower? Will the database rebuild the index automatically? When? What is the command to trigger an index rebuild manually. Is the index rebuild kind of a "stop-the-world" operation, so that BaseX will become unresponsive or will it be done in parallel. What are the benefits of the indices, can I live without them?
-- Antoni Myłka Software Engineer
basis06 AG, Birkenweg 61, CH-3013 Bern - Fon +41 31 311 32 22 http://www.basis06.ch - source of smart business
----- Ursprüngliche Mail ----- Von: "Christian Grün" christian.gruen@gmail.com An: "Antoni Mylka" amy@basis06.ch Gesendet: Dienstag, 20. November 2012 16:46:30 Betreff: Re: [basex-talk] Database corruption
Hi Antoni,
I'll also try to run an experiment without UPDINDEX.
yes, this would be interesting. I did some more testing with the given queries, but couldn’t encounter something noteworthy so far..
Thanks, Christian