gridengine.info

Consider this snippet more search engine fodder for people web searching on particular error messages.

Recently a user asked on the mailing list about encountering job submission rejection messages that say:

job dropped because of user limitation

That particular rejection message is tied to 2 different configuration parameters that can be hard coded into grid engine:

The number of active (not finished) jobs which each Grid Engine user can have in the system simultaneously is controlled by this parameter. A value greater than 0 defines the limit. The default value 0 means "unlimited". If the max_u_jobs limit is exceeded by a job submission then the submission command exits with exit status 25 and an appropri- ate error message.

The number of active (not finished) jobs simultaneously allowed in Grid Engine is controlled by this parameter. A value greater than 0 defines the limit. The default value 0 means "unlimited". If the max_jobs limit is exceeded by a job submission then the submission command exits with exit status 25 and an appropriate error message.

Commentary: There are certainly use cases for which these parameters are the best solution but ... before using either of them, consider if one of the SGE resource allocation policy mechanisms can accomplish the same goals. Hard coding global constraints on jobs can negatively affect flexibility and overall system utilization.