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

[Steffen Grunewald <steffen.grunewald@xxxxxxxxxx>]

On Fri, 2017-07-14 at 09:51:56 -0500, Tom Downes wrote:
> Greg:
> 
> 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.

There are Debian installations and derivatives which do not use systemd,
or limit its use to a minimum. 

Just saying,

 S

> --
> Tom Downes
> Senior Scientist and Data Center Manager
> Center for Gravitation, Cosmology and Astrophysics
> University of Wisconsin-Milwaukee
> 414.229.2678
> 
> 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
> > <https://www-auth.cs.wisc.edu/lists/htcondor-users/2017-April/msg00059.shtml>
> > ).
> > 2. configure the kernel to be able to use cgroups correctly (mine
> > <https://www-auth.cs.wisc.edu/lists/htcondor-users/2017-April/msg00062.shtml>
> > )
> >
> >
> > FWIW, we'll fix HTCondor so that it does better detection of cgroups on
> > Debian and doesn't hang in future releases.
> >
> > -greg