Hi John,
I agree with Peter that these are almost certainly WMS jobs from Ganga.
However, I'm not sure why the protocol that's used is causing problems as
I thought Johannes Elmsheuser (GangaAtlas dev, CC'ed) fixed this in recent
releases. Johannes: could you comment on why jobs at Liverpool would be
causing these problems?? This is definitely your area rather than mine!
Thanks,
Mark
On Tue, 9 Mar 2010, Peter Love wrote:
> You're essentially talking about jobs via WMS, users are probably
> using ganga with LCG backend. Stop advertising that queue for atlas
> and that should do the trick. Pilots won't be affected.
>
> Peter
>
> On 9 March 2010 09:28, John Bland <[log in to unmask]> wrote:
>> Hi,
>>
>> We've been seeing a few ATLAS users submitting analysis jobs to our site
>> directly, rather than via the pilot systems.
>>
>> The problem with is that the users may not necessarily know which access
>> method to use at any particular site. The jobs we've seen have been using
>> direct RFIO access and even a small number of jobs are either saturating the
>> IOPS on the pools (small buffers) or saturating switches (big buffers).
>>
>> This is with only a relatively small number of jobs, a site full of them
>> would simply grind to a complete halt for days and be an enormous mess for
>> all concerned.
>>
>> Is there any way of getting around this other than ticketing every single
>> user that does it (or fixing ATLAS AOD read patterns ;0)?
>>
>> John
>>
>> --
>> John Bland [log in to unmask]
>> System Administrator office: 220
>> High Energy Physics Division tel (int): 42911
>> Oliver Lodge Laboratory tel (ext): +44 (0)151 794 2911
>> University of Liverpool http://www.liv.ac.uk/physics/hep/
>> "I canna change the laws of physics, Captain!"
>>
>
|