[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [HTCondor-users] condor_starter processes at 100% CPU on Debian after completing job, before transferring files back


It might be worth your poking the debian testing/experimental folks about why they still choose to turn off the memory controller by default. The previously stated reason was that virtual memory performance was impaired when it was turned on but left unused. Assuming this is actually true, in init.d-land that would be a reasonable frequent -- and bad -- outcome. In systemd-land, I think the merits of that choice are much lower.

I'm not sure what happens if one enables cgroups-v2 either.

Anyhow, fixing it in the Debian future release would fix it in Debian "forever" and perhaps derivative platforms like Ubuntu would follow.

Tom Downes
Senior Scientist and Data CenterÂManager
Center for Gravitation, Cosmology and Astrophysics
University of Wisconsin-Milwaukee

On Fri, Jul 14, 2017 at 9:40 AM, Greg Thain <gthain@xxxxxxxxxxx> wrote:
On 07/14/2017 07:58 AM, Tom Downes wrote:
You'll want to read the entire thread. The options are:

1. disable cgroups entirely (Greg's suggestion).
2. configure the kernel to be able to use cgroups correctly (mine)

FWIW, we'll fix HTCondor so that it does better detection of cgroups on Debian and doesn't hang in future releases.


HTCondor-users mailing list
To unsubscribe, send a message to htcondor-users-request@cs.wisc.edu with a
subject: Unsubscribe
You can also unsubscribe by visiting

The archives can be found at: