Berkeley DB Family

I have a tool which I run when I end up with a large cleaner backlog. It's based on some sample code I fished out of the forum, and it basically just opens the environment, optionally deletes a couple of expendable databases, manually runs the cleaner in several threads until the backlog is gone, and closes the environment. (Both je.env.runCleaner and je.env.runCheckpointer are set to false.)

I've noticed that in some cases the INCompressor thread keeps running after the final checkpoint has finished, leading to a very large recovery time when the environment is next opened (because a lot ends up being written to the log after the last checkpoint). I presume this is due to the large number of cleaner threads.

(I see that early in the environment close code, the daemon threads are notified to exit, but the INCompressor code doesn't check this flag until after it has finished a set of work items, and I'm guessing it's working through a very long list.)

As a test, I set je.env.runINCompressor to false for a run of my tool, and in this case the environment closes quickly and also subsequently opens quickly. But I don't know what the consequences are, of not running the INCompressor thread at all during this operation. Is this safe to do? Does it cause bloat in the log files (because it's skipping some sort of cleanup)?

I didn't see any way to manually wait for the INCompressor thread to terminate before issuing a final checkpoint, so disabling the INCompressor thread was the only workaround I could think of.

(This is under JE 4.1.17.)