As reported in a separate thread, I’m still getting the optimization failure for large databases but not smaller ones. This behavior is consistent in my tests.
Cheers,
E.
_____________________________________________
Eliot Kimber
Sr Staff Content Engineer
O: 512 554 9368
M: 512 554 9368
LinkedIn | Twitter | YouTube | Facebook
From:
Christian Grün <christian.gruen@gmail.com>
Date: Friday, March 1, 2024 at 9:30 AM
To: Eliot Kimber <eliot.kimber@servicenow.com>
Cc: BaseX <basex-talk@mailman.uni-konstanz.de>
Subject: Re: [basex-talk] Optimize database never returns, leaves database in "opened by another process" state
Glad to hear it, thanks Eliot.
Eliot Kimber <eliot.kimber@servicenow.com> schrieb am Fr., 1. März 2024, 16:21:
Using the 27-02-2024 build I have confirmed that the optimize database deadlock seems to be resolved.
I was able to easily upgrade my code to replace prof:dump() with message() and db:open() with db:get() and everything else seems to be working as it should.
I like the new Editor replacement for the old Query feature in the DBA app.
Cheers,
E.
_____________________________________________
Eliot Kimber
Sr Staff Content Engineer
O: 512 554 9368
M: 512 554 9368
From: Christian Grün <christian.gruen@gmail.com>
Date: Wednesday, February 28, 2024 at 9:36 AM
To: Eliot Kimber <eliot.kimber@servicenow.com>
Cc: basex-talk@mailman.uni-konstanz.de <basex-talk@mailman.uni-konstanz.de>
Subject: Re: [basex-talk] Optimize database never returns, leaves database in "opened by another process" state[External Email]
…this one could be related to a bug that was recently fixed in the latest snapshot [1]. About time to get BaseX 11 finished…
On Mon, Feb 26, 2024 at 5:25 PM Eliot Kimber <eliot.kimber@servicenow.com> wrote:
Using Basex 10.7 on Linux.
I’m running a sequence of jobs to update and optimize a set of databases following loading a number of documents created dynamically (as opposed to being read from disk).
I’m seeing a new behavior, which is that the optimization step never completes but also doesn’t show any error in the log. The database shows no items and is in the locked by another process state if I try to drop it. This behavior seems to be consistently repeatable with my current code base (I’m working on some code updates, so it’s possible I’ve introduced something that would cause this behavior but I haven’t changed the code that leads up to the failing optimize). The server has plenty of disk space, etc.
Optimization code is:
try {if (db:exists($database))
then
(
util:logToConsole('dbadmin:optimizeDatabase', ``[Optimizing database `{$database}`]``),
db:optimize($database, true(), $dbadmin:dbOptimizeOptions)
)
else util:logToConsole('dbadmin:optimizeDatabase', ``[Database '`{$database}`' does not exist. Nothing to optimize.]``)
} catch * {
util:logToConsole(
'dbadmin:optimizeDatabase',
``[Exception optimizing database '`{$database}`': `{$err:code}` - `{$err:description}`]``,
'error')
}
And the optimization options are:
declare variable $dbadmin:dbOptimizeOptions as map(*) :=(: Turn on all the indexes :)
map {
'attrindex' : true(),
'tokenindex' : true(),
'textindex' : true(),
'ftindex' : true()
};
This code has been working fine for a long time and I’ve been running 10.7 for a least a couple of months, so I’m wondering:
A) Would would cause this behavior?
B) How can I diagnose it short of debugging the Java code (which I can do but it’s non-trivial for me to set up).
Thanks,
Eliot
_____________________________________________
Eliot Kimber
Sr Staff Content Engineer
O: 512 554 9368
M: 512 554 9368