Job Queue database lock file appearing when I open multiple engines

Hello, 

I am using ContextCapture Center edition (Update 20.1 - v10.20.1.5562) and have been starting to experience issues in the last week (was running previous version when the issues started) of the job queue data base file locking when I open another engine on my network. When this file appears, whatever process is running - both ATs and Reconstructions - seem unable to access the job queue ('Job Queue Not Reachable') and it goes back to 'Pending,' and then the job queue monitor will show 0 engines.

Right now, I have quite a large Reconstruction which I'm able to build using only this computer's engine. I can't recall if this issue has happened when I have only been running an Aerotriangulation only. It seems to be a problem mostly when I am doing reconstructions, or at least this is when I have noticed it. 

A few notes:

  • I have tried moving the project job queue to another computer's directory with the same issue happening.
  • I have noticed this problem has started either during 'Production Preparation' when the project fails and the job queue becomes locked, or when I have tried to change the job queue priority.
  • I have tried cancelling all jobs, and closing all engines to remove the lock file, and deleting the engine and job queue files, then restarting the job and all of the engines in the cluster. This worked for a few reconstructions, but is no longer working.
  • I have tried re-starting every machine and have upgraded to the latest version on all machines
  • As an update - this problem only occurred when I selected regular volumetric grid as the tiling for the reconstruction. I tried quite a few different tile sizes, and it seemed like it didn't make a huge difference. I suspect this had something to do with too much read/write traffic on my network. When I reverted to my standard setting of 'adaptive tiling' this problem immediately resolved itself.