I don't think there is or can be anything general. This is something the system accepting and scheduling the jobs has to do. If you have the source code, find the best places where a disk space check could be added and jobs either rejected or postponed. If there is a way to "pause or otherwise modify submitted jobs" it depends on the scheduler. If we don't know what do you use, we can't help.

Also keep in mind that blindly pausing all jobs might not help. There may be jobs producing a lot of data, jobs using lots of temporary space, but also jobs that aggregate data produced by other jobs and if you pause those, you are eventually going to run out of space anyway as there will be nothing that'd clean up the produced intermediary results. You need to know the scheduler and you need to know the jobs!

You didn't say exactly what OS you're using, but have you might try using quota, it should be built into your version of linux/unix and you just have to configure it & turn it on.

A quick google search will turn up lots of info about "linux quota" for example, or ask your local sysop.

There are many job-monitor systems out there for Unix and Linux, and one of the things they can regulate is “expected disk-space usage.”   But they really can’t observe how much disk space any particular job is using, nor can they necessarily regulate it (even with quota).   You need to know the jobs.

Many shops try to do job scheduling with crontabs, and they get into trouble because you really can’t predict the completion-time of one unit of work.   You wind up either wasting time or doubling-up on resources.

So-called “workflow monitoring” systems can be surprisingly effective.   The various components of what we call “jobs” can in fact all run as child-processes of a parent that is simply forking children and waiting for them to complete.   Heck, if the workflow is predictable and unchanging, that can be how you run jobs with a great deal of control, e.g. driven by a Perl script.   All the work is done under the auspices of one parent pid.

Clumsy pseudo-pseudo-code... from one who doesn't work with clusters... nor have any ken of their peculiarities, but could something like this conceivably work?

# monitor disk space in a cluster

# create @list_machines -- which do you need to check

my $i = 0; # create counter (flag)

for $_(@list machines) {
    my $machine = $_;   # select machine  # This and the next line == 
+the WEAK POINTS?
    # log in/open $machine 
    # if necessary, my @dirs = selection of dirs to check for change
    my $dir (@dirs) {
        readdir the  dirs in preceding line;         # dir /as for win
+  to obtain dir of all files in all subdirs 
        write dir results to local RAM file, $dir.$machine.$i
        $i++;
        if ( $i == 2 ) { 
            $i = 0; 
        }
        next;
    }
}

sleep (some amount of time);

for $_(@list machines) {
    my $machine = $_;   # select machine  
    if ( (exists $dir.$machine.0) && (exists $dir.$machine.1) ) {
        compare those two files (diff, df, pure-perl list comparison)
        ...PROFIT...
    }
}
[download]