[gridengine users] Start jobs on exec host in sequential order
klin938 at gmail.com
Fri Jul 27 01:14:55 UTC 2018
We are using $JOB_ID as xfs_projid at the moment, but this approach
introduces problem to array jobs whose tasks have the same $JOB_ID (with
Also it is possible that tasks from two different array jobs run on the
same node contain the same $TASK_ID, thus the uniqueness of the $TASK_ID on
the same host cannot be maintained.
That's why I am trying to implement the xfs_projid to be independent from
On Thu, Jul 26, 2018 at 9:27 PM, Reuti <reuti at staff.uni-marburg.de> wrote:
> > Am 26.07.2018 um 06:01 schrieb Derrick Lin <klin938 at gmail.com>:
> > Hi all,
> > I am working on a prolog script which setup xfs quota on disk space per
> job basis.
> > For setting up xfs quota in sub directory, I need to provide project ID.
> > Here is how I did for generating project ID:
> > XFS_PROJID_CF="/tmp/xfs_projid_counter"
> > echo $JOB_ID >> $XFS_PROJID_CF
> > xfs_projid=$(wc -l < $XFS_PROJID_CF)
> The xfs_projid is then the number of lines in the file? Why not using
> $JOB_ID directly? Is there a limit in max. project ID and the $JOB_ID might
> be larger?
> -- Reuti
> > My test shows, when there are multiple jobs start on the same exec host
> at the same time, the prolog script is executed almost the same time,
> results multiple jobs share the same xfs_projid, which is no good.
> > I am wondering if I can configure the scheduler to start the jobs in a
> sequential way (probably has a interval in between).
> > Cheers,
> > Derrick
> > _______________________________________________
> > users mailing list
> > users at gridengine.org
> > https://gridengine.org/mailman/listinfo/users
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the users