Skip to content
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

BITMAKER-1932: API control max number of simultaneous jobs #63

Open
wants to merge 9 commits into
base: main
Choose a base branch
from

Conversation

mgonnav
Copy link
Member

@mgonnav mgonnav commented Aug 17, 2022

Description

Control from the API how many jobs are running simultaneously and scale this number according to the current scale of our job manager engine (for Kubernetes, the number of available nodes).

Issue

Checklist before requesting a review

  • I have performed a self-review of my code.
  • My code follows the style guidelines of this project.
  • I have made corresponding changes to the documentation.
  • New and existing tests pass locally with my changes.
  • If this change is a core feature, I have added thorough tests.
  • If this change affects or depends on the behavior of other estela repositories, I have created pull requests with the relevant changes in the affected repositories. Please, refer to our official documentation.
  • I understand that my pull request may be closed if it becomes obvious or I did not perform all of the steps above.

mgonnav and others added 9 commits October 14, 2022 15:34
* Add lifespan & total_response_bytes fields to SpiderJob.
* Add UsageRecord model.
* Add endpoint to get UsageRecords in a date range and current project usage.
* Use DatabaseInterface
* Create usage records per project based on events (completed job, delete data)
* Do not delete the project but use a flag deleted to keep usage records
* Add item_count and request_count to SpiderJob
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.

1 participant