Skip to content

@Ekam219: Added activeDeadlineSeconds for Kubernetes Job Resource Management Description #973

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

DonggeLiu
Copy link
Collaborator

@DonggeLiu DonggeLiu commented Apr 8, 2025

Changes:
Added activeDeadlineSeconds: 43200 (12 hours) to the second Kubernetes job configuration. This prevents the job from running indefinitely and reduces resource consumption.

Based on: #943

DonggeLiu and others added 2 commits April 8, 2025 17:02
…scription: (#943)

@DonggeLiu 
This pull request addresses an issue in the pr-exp.yaml file, where the
second Kubernetes job was missing the activeDeadlineSeconds field. The
absence of this field could have caused the job to run indefinitely,
consuming excessive resources and leading to unpredictable behavior.
This fix ensures that both jobs have the same resource management
strategy.

Changes:
Added activeDeadlineSeconds: 43200 (12 hours) to the second Kubernetes
job configuration. This prevents the job from running indefinitely and
reduces resource consumption.

Fix:
By adding this field, we align the second job’s configuration with the
first job, which already has a similar field, ensuring consistent
resource management across both jobs.

Additional Notes:
The change aims to prevent excessive resource consumption by limiting
the runtime of the job to 12 hours. This is a more reasonable timeframe
compared to the original 7 days, ensuring better resource allocation for
quicker jobs.
#931
@DonggeLiu
Copy link
Collaborator Author

/gcbrun exp -n ej -ag

@DonggeLiu
Copy link
Collaborator Author

Hi @Ekam219, could you please take a look at the error at your convenience?
Thanks : )

Step #3: error: error parsing /opt/oss-fuzz-gen/k8s/pr-exp-sub.yaml: error converting YAML to JSON: yaml: line 23: did not find expected key

@DonggeLiu DonggeLiu marked this pull request as draft April 10, 2025 03:27
@Ekam219
Copy link

Ekam219 commented Apr 12, 2025

Hi @DonggeLiu,
My final exams are currently going on, but I'll make sure to look into this as soon as I get some time. Appreciate your patience!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants