Ensuring two jobs cannot run on the same node

Hi @Eambo !

The original question was interesting to me, because I needed something similar. Framed a different way, you need to know facts about other jobs.

I needed to know facts about other nodes in a job:

… to me these are similar kinds of questions, meaning that they would consume similar types of data.

However,

I interpret this to mean that Job A’s state blocks Job B’s state? That sounds like you want inter-task dependencies…

If on the other hand this is the central problem:

then it seems like you need to look up information about a different job before submitting one. This may be a smell that you’re “doing it wrong” – either not abstracting the application in the job properly, colliding ports, etc. But if these are the same job, just different allocations, then perhaps the distinct_hosts operator is what you’re looking for? This might work well for parallel executions of a task in a job.

Does any of this hit home?