Hello!
We've got two Engines (FME Server 2020.1.0.1).
The workspace accesses files which could be accessed by only one editor. But the workspace can be started by many users.
How do I prevent running the same workspace at the same time on both engines?
The FME Server should detect whether the workspace is running. If the workspace is running, the new job shall be queued.
Thank you for your help!
Your best bet it to create a separate queue for this workspace - Assign just one engine to the queue. https://docs.safe.com/fme/html/FME_Server_Documentation/WebUI/Queue-Control.htm - in this case the workspace will only be run on that one engine, if the engine is already in use it will go into the queue.
the downside here though is that if you are running a different job with that engine then the job will still be queued.
Hi @momo ,
One way you could do it is by creating a Queue specifically for this workspace and then assigning it to one of your engines. Look under Engines - Queues - Create Queue. This way any jobs triggered to run this workspace will always go to the same engine and therefore will run one after the other, not at the same time.
https://docs.safe.com/fme/html/FME_Server_Documentation/WebUI/Queue-Control.htm
Thank you both for your suggestion - this is a good solution although it's not perfect!
@virtualcitymatt "the downside here though is that if you are running a different job with that engine then the job will still be queued." -> That's true. My workaround for that is to divide the two engines: one engine for fast jobs, the other for time consuming jobs.