So this happened again overnight but I have more information now.
1) I had switched off UPDINDEX on some of the databases and one of these was
affected so this is not an UPDINDEX issue
2) I found that there was a hard crash of the JVM - which would account for why
many databases were left locked
Christian,
I can’t reliably reproduce the behaviour at all at the moment but I’m losing a
fair number of databases to the problem. I first thought it was related to
running out of disk space mid-operation but I don’t think that’s the cause. I
just wanted to check that I wasn’t doing anything I
> So another question - these seem to come about from running OPTIMIZE ALL on
> databases with UPDINDEX TRUE. Is there any reason that OPTIMIZE ALL can’t be
> run on such databases?
It shouldn’t cause any problems. Here is a little command scripts that
demonstrates that it should work alright:
Hi Christian,
Thank you for that - so I’m looking in the right area.
> As you already guessed, these folders are relics from OPTIMIZE ALL
> calls – or db:optimize($db, true) –, and they are removed after the
> operation if everything went alright.
So another question - these seem to come about
Hi James,
As you already guessed, these folders are relics from OPTIMIZE ALL
calls – or db:optimize($db, true) –, and they are removed after the
operation if everything went alright.
Hope this helps,
Christian
On Fri, Jan 8, 2016 at 12:25 PM, James Ball wrote:
> Hello,
>
> I’m seeing regular o
Hello,
I’m seeing regular occurrences where I end up with extra folders in my database
location with numbers after, for example:
ODF-PUSH-T-JU
ODF-PUSH-T-JU_1079560404
These have some but not all of the files from the original database with the
same name, crucially don’t have the inf.basex fil
6 matches
Mail list logo
