[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [HTCondor-users] exclude a domain ?
- Date: Wed, 21 Oct 2015 14:35:40 -0500
- From: Todd Tannenbaum <tannenba@xxxxxxxxxxx>
- Subject: Re: [HTCondor-users] exclude a domain ?
On 10/19/2015 8:50 AM, Michael V Pelletier wrote:
"HTCondor-users" <htcondor-users-bounces@xxxxxxxxxxx> wrote on
10/19/2015 07:50:22 AM:
> Please pardon my asking this instead of just testing it which I will
> to do anyway.
> But I would like to get it right the first time.
> Is function "regexp" full featured so that it will accept something like:
> requirements = regexp("<123\.456\.|184.108.40.206",StartdIpAddr)==False
> requirements =
> Is there a limit to the length of the string?
HTCondor uses Perl-Compatible Regular Expressions - the PCRE library - so
you have all the options you'd have in a Perl script, including |, +,
character ranges, and everything else.
Having started with regexps on UNIX System III, I still sometimes wind up
with over-complicated expressions that don't use all the newfangled regexp
Any length limitation would be imposed by PCRE, and as I recall it's too
large to make a difference in nearly all use cases.
One thing to keep in mind is if you have huge/complex regular
expressions in your job policy expressions, it will of course have an
impact on the performance of the condor_schedd and/or the
condor_negotiator if you submit enough (many thousands) of jobs. How
much of an impact? I cannot precisely say, but I'm curious enough to
have a student here do some plots to answer that question. My educated
guess is the impact will be relatively insignificant (especially if the
jobs group into a small number of autoclusters), but I don't have hard
data to back up that claim.