CRAB3 periodic remove expression checks for "MemoryUsage" classAd in the running jobs. When a job gets routed to "Grid Universe", this classAd is dropped causing CRAB3 job to go to hold with the following reason:
The job attribute PeriodicRemove expression
Can we modify this expression on one of the testbed taskworkers? Maybe replace
( MemoryUsage > RequestMemory )
with
ifthenelse(MemoryUsage is undefined, false, MemoryUsage > RequestMemory)
I am open to suggestions on how else to fix this. Right now I think hard coding any value should be okay? I need to be sure that we don't hit another bottleneck.
Hi,
CRAB3 periodic remove expression checks for "MemoryUsage" classAd in the running jobs. When a job gets routed to "Grid Universe", this classAd is dropped causing CRAB3 job to go to hold with the following reason: The job attribute PeriodicRemove expression
Can we modify this expression on one of the testbed taskworkers? Maybe replace
with
I am open to suggestions on how else to fix this. Right now I think hard coding any value should be okay? I need to be sure that we don't hit another bottleneck.
Farrukh