If the job had consciously been writing data to your SE then you may
have been able to set quotas for a VO stopping them affecting others but
this was the log of the job so that wouldn't help. Do stdout/err get
cached by your batch system until job end or do they grow in the users
$HOME? Can't you set a batch system parameter to curtail logs?
John
> -----Original Message-----
> From: Testbed Support for GridPP member institutes
> [mailto:[log in to unmask]] On Behalf Of David Robson
> Sent: 17 April 2007 16:27
> To: [log in to unmask]
> Subject: Quotaing grid accounts
>
> The EFDA-JET site has just been hit by a series of very
> verbose jobs that have created over a Terabyte of output over
> the weekend, filling up our disks and consequently raising
> the load on our CE and Se to several hundred.
> (See https://gus.fzk.de/pages/ticket_details.php?ticket=20833).
>
> The problem is now resolved, but could reoccur. The obvious
> solution is to quota the grid accounts. Do people do this,
> and what size of quota do you recommend?
>
> Cheers
>
> Dave Robson
> EFDA-JET administrator
>
|