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

Re: [HTCondor-users] cgroup setup with centOS7/systemctl?



Hi Brian,

many thanks - that clears things up!

Yes, I am still somewhat wired to SysV ;) - but I see that Systemd can
have its advantages (at least I have already managed some simple service
unit files which are imho more accessible than init-services) - still
some learning curve ahead to get into the depth of systemd

Cheers and thanks,
  Thomas

ps:
for completness/documentation
with
  BASE_CGROUP=/system.slice/condor.service
the jobs' resource controls/info go to

/sys/fs/cgroup/*/system.slice/condor.service/condor_var_lib_condor_execute_slot*
- it took me some time to realize the path ;)

On 2017-03-15 15:19, Brian Bockelman wrote:
> Hi Thomas,
> 
> I think this would now all go into site-local overrides for the HTCondor unit files.
> 
> If you find yourself doing anything cgconfig related, you're fighting a 100% losing battle as time goes forward.
> 
> Going off memory, I think you can simply set in the condor config:
> 
> BASE_CGROUP=/system.slice/condor.service
> 
> and you're done -- no other services to run.
> 
> If, for example, you want all of HTCondor to have a limit of 16GB of RAM, you would create the following directory (see https://www.freedesktop.org/software/systemd/man/systemd.unit.html):
> 
> /etc/systemd/system/condor.service.d
> 
> and then create a file /etc/systemd/system/condor.service.d/99_local.conf with the following contents:
> 
> [Service]
> MemoryLimit=16G
> 
> (see https://www.freedesktop.org/software/systemd/man/systemd.resource-control.html).
> 
> While this is indeed a new approach to learn, the upside is that this works across the entire range of system services -- and the config file format / rules is shared with huge swaths of the system!
> 
> Brian
> 
>> On Mar 13, 2017, at 4:51 AM, Thomas Hartmann <thomas.hartmann@xxxxxxx> wrote:
>>
>> Hi all,
>>
>> with /etc/cgconfig.conf being deprecated under CentOS7/systemctl, I
>> wonder if there is already a 'canonical' approach on how to setup/run
>> cgroup configs for Condor under systemctl?
>>
>> Would be creating an overall unit for condor (or setting resources via
>> systemctl set-property for condor.service) the way to go?
>> I suppose jobs will be in the condor.service cgroup - would additional
>> steps be necessary for setting any job resources (systemd-run?)?
>>
>> Cheers and thanks,
>>  Thomas
>>
>> _______________________________________________
>> HTCondor-users mailing list
>> To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
>> subject: Unsubscribe
>> You can also unsubscribe by visiting
>> https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users
>>
>> The archives can be found at:
>> https://lists.cs.wisc.edu/archive/htcondor-users/
> 
> _______________________________________________
> HTCondor-users mailing list
> To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
> subject: Unsubscribe
> You can also unsubscribe by visiting
> https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users
> 
> The archives can be found at:
> https://lists.cs.wisc.edu/archive/htcondor-users/
> 

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature