Bug #5410
closedprovenance data is not flushed to HSQL database before Kepler quit.
0%
Description
Currently, provenance data writing to HSQL database has write delay (100 ms by default). It causes some data is not update or written because the data is not flushed before Kepler quit.
To reproduce it,
1) Run workflow in Kepler GUI or non-GUI mode.
2) Quit Kepler if Kepler is run in GUI mode right after workflow is executed.
3) Use HSQL client to connect hsql provenance database.
4) Check 'workflow_exec' table: the record the execution might not be written in the database or the execution status might be always 'running'.
It should work for both GUI mode or non-GUI mode. Not sure whether it works for other databases, such as Oracle and mySQL.
Updated by Derik Barseghian almost 13 years ago
I'm a little surprised you're seeing this with write_delay at 100ms. Have you tried 0 to see if it's truly the problem? I set write_delay to 100ms at r20931 (see bug#4325) to avoid a similar problem, and that was fast enough. Lowering it is probably fine, but keep an eye out for performance issues - e.g. does workflow execution speed slow down as it waits for writes to provenance?
Updated by jianwu jianwu almost 13 years ago
I discussed this issue with Dan. He confirmed the bug. My test is done in non-GUI mode, so Kepler exit right after workflow execution is done.
I know set write delay to be 0 will slow down workflow execution, maybe quite a lot. So a better way is to keep some write delay and flush data before Kepler exit.