Now the stuck job got released when I deleted a job that was after it in the queue. The jobs seem to get stuck in packs, never alone.
On Mar 20, 12:45 pm, Daniel Tkatch <daniel.tka...@smeet.com> wrote: > Recently, I am experiencing a weird issue. > > I have a job whose execution is restricted to a specific node. This > job keeps waiting in the queue even though the node became active. It > seems to be stuck in the queue for a while (several minutes) and gets > released after some time. Hmm.. > > Any idea what could be causing this? Where should I start looking?
