LHC Computer Grid - Rollout
> [mailto:[log in to unmask]] On Behalf Of Jean-Michel Barbet
said:
> I applied the last gLite updates to our LCG-CE. I noticed that the
> attributes GlueCEPolicyMax[ObtainableCPUTime,RunningJobs,WaitingJobs,
> TotalJobs,SlotsPerJob] have changd from 0 to 999999999.
>
> => Is this expected ?
Yes. This is the default when you have no limit set (or at least the
info provider thinks you haven't!). A large value makes more sense than
0 as a default for these things, e.g. if someone puts a requirement on,
say, WaitingJobs < MaxWaitingJobs you don't need a special treatment for
zero.
> => Should try to find how to publish correct values ?
Well, you should think about whether you want to set limits, e.g. many
sites set limits on WaitingJobs (i.e. the maximum number of queued jobs)
to prevent very long queues building up. The "max obtainable" values are
the limits that you could get if you ask the batch system explicitly -
traditionally we haven't been able to use that with the RB and WMS
because they gave you no way to pass requests to the batch system. I
think there is now supposed to be a way to do that but I'm not sure of
the status. MaxSlotsPerJob relates to MPI jobs, but I'm not an expert on
that and I know there are other problems with the use of glue for MPI,
e.g. the way CPU time limits are treated.
Stephen
--
Scanned by iCritical.
|