> On Jan 27, 2020, at 10:52 PM, Allen Wittenauer > <a...@effectivemachines.com.INVALID> wrote: > > This is almost always because whatever is running on the two executors > have suffocated the system resources. ... and before I forget, a reminder: Java threads take up a file descriptor. Hadoop's unit tests were firing up 10s of thousands of threads which were eating up 10s of thousands of FDs and ultimately lead to "cannot fork, no resource" errors causing everything to come tumbling down for the Jenkins salve process. So _all_ the resources, not just RAM or whatever.
- Re: broken builds taking up resources Martin Stockhammer
- Re: broken builds taking up resources Mick Semb Wever
- Re: broken builds taking up resources Mick Semb Wever
- Re: broken builds taking up resources Chris Thistlethwaite
- Re: broken builds taking up resource... Mike Jumper
- Re: broken builds taking up res... Gavin McDonald
- Re: broken builds taking up resource... Chris Lambertus
- Re: broken builds taking up res... Chris Lambertus
- Re: broken builds taking up... Andriy Redko
- Re: broken builds taking up... Allen Wittenauer
- Re: broken builds taking up... Allen Wittenauer
- Re: broken builds taking up... Chris Lambertus
- Re: broken builds taking up... Allen Wittenauer
- Re: broken builds taking up... Chris Lambertus
- Re: broken builds taking up res... Alexey Markevich
- Re: broken builds taking up resources Zoran Regvart
- Re: broken builds taking up resources Ismael Juma