[GE users] manage NFS resources

markhewitt mh613 at york.ac.uk
Wed Sep 9 15:12:28 BST 2009

> You mean $TASK_ID?


> That would work if you know the time the input loading is finished. That 
> time can be calculated if you assume that no other job is using the 
> fileserver at the same time and if you know what files will be loaded. 
> Instead of starting the subjobs and having them sleep I also could give 
> them a varying start time. So they could leave room for other jobs which 
> hopefully use other fileservers.
> But I still have no tool to make sure the bandwidth to the fileserver is 
> not exhausted. Could a load_sensor be of help? Would then every job 
> request some needed bandwidth (and the time this bandwidth is needed) I 
> have a hard time imaging any solution to this.

Sure it's a crude way of doing it and the load on the file server will 
likely spike but c'est la vie.

Another technique you could use a lock file. Quite simply when the first 
job starts reading in the data it creates a file, an empty file is 
sufficient, then when it's finished reading the data it deletes the file.

All jobs can then have a while loop which said while the lock file 
exists, sleep for (say) 60 seconds, then try again.

That would at least ensure there is only one node accessing the file 
server at any one time.


To unsubscribe from this discussion, e-mail: [users-unsubscribe at gridengine.sunsource.net].

More information about the gridengine-users mailing list