From: tech.vronk <te...@vr...> - 2012-05-17 14:54:37
|
Hi Wolfgang, thank you for the information. Is there anything I can do meanwhile preemptively, to prevent this from happening again, like restarting the database or running the consistency checks more often? Or meanwhile just backup often enough, check the queries twice before running and pray? thanks again. matej Am 17.05.2012 10:52, schrieb Wolfgang Meier: > Hi, > >> I have experienced quite problematic behaviour of the exist-db lately. >> >> I have the 2.0-tech-preview version running. >> >> After an (obviously) inefficient query that ran for ever, >> on next start >> the 'exist' instance" could not be found. > I had a similar issue the other day: probably a deadlocked thread > which prevented eXist from creating a checkpoint for several days. > Upon restart I had a huge transaction log, which fortunately was ok > and the data could be restored by recovery. > > Normally eXist should create a checkpoint when the last write > transaction completes, but it seems we have a problem here in 2.x., > resulting in a risky recovery run whenever you have to kill the db. > I'm looking into this today. > > Wolfgang > > |