What is the proper name for "ghost" jobs and how are they controlled?

[John Bobinyec]

We have a pool of slaves.  When a job is dispatched to one of them it is assigned to an executor on that machine.  Oftentimes there is a very similar job running on another machine but it's not assigned to an executor.  I call these ghosts.  What do they do?  How are they dispatched?  It seems like they interfere with the jobs which are supposed to be running on that machine, because real jobs which are destined for that machine get queued up.

Thanks,
jb

[John Bobinyec]

The apparent interference might have been due to other things.

But does no one else have ghosts?

jb

[Eric Pyle]

I think you are referring to so-called flyweight executor tasks. For example, the parent task of a multi-configuration project. Because such tasks typically don't require many system resources, they do not occupy an executor. I have seen cases on our Jenkins installation where the flyweight tasks did seem to cause other jobs to queue up, even though they should not. We worked around it by creating a couple of Linux agents/slaves with multiple executors and tying all the parent jobs to those agents (requires the Matrix Tie Parent plugin).

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/335ed9c7-ea23-4eec-9ceb-0b75cfcc4fe2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Eric Pyle

Siemens PLM Software

Lebanon, NH

+1 603-277-3060 (T)

+1 603-359-8670 (M)

eric...@siemens.com

http://www.siemens.com/plm