Configure Job Submission
Installation
For PrimeHub EE, the job submission is enabled by default. Here is the advanced configuration for job submission
Job Settings
jobSubmission.workingDirSize
5Gi
jobSubmission.defaultActiveDeadlineSeconds
Default timeout (seconds) for a running job
86400
jobSubmission.defaultTTLSecondsAfterFinished
Default TTL (seconds) to delete the pod for a finished job
604800
jobSubmission.nodeSelector
{}
jobSubmission.affinity
{}
jobSubmission.tolerations
[]
jobSubmission.jobTTLSeconds
the retention of a job that it will be kept in PrimeHub after the job (succeeded, failed, cancelled). The default value is 30 days. Zero value means unlimited.
2592000
jobSubmission.jobLimit
The limit of total amount of jobs, the oldest job will be removed if the limit is exceeded; Zero value means unlimited.
4000
Example:
Job Artifacts
jobSubmission.artifact.enabled
If the job artifact feature is enabled
true
jobSubmission.artifact.limitSizeMb
The total size of artifacts a job can upload
100
jobSubmission.artifact.limitFiles
The total files a job can upload
1000
jobSubmission.artifact.retentionSeconds
How long would the artifacts preserve
604800
Example:
Log Persistence.
By default, the job submission log is persistent for 7 days (configured by jobSubmission.defaultTTLSecondsAfterFinished
). The log is removed once the underlying pod is deleted. Log persistence feature allows to upload log to primehub store.
store.enabled
If the PrimeHub store is enabled
false
store.logPersistence.enabled
If the log persistence is enabled
true
fluentd.flushAtShutdown
false
fluentd.flushInterval
3600s
fluentd.chunkLimitSize
"256m"
fluentd.storeAs
txt
fluentd.*
The other fluentd settings
Last updated