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

Separate 832 move.py new_file and pruning work queues, set priorities #38

Open
davramov opened this issue Oct 22, 2024 · 0 comments
Open

Comments

@davramov
Copy link
Contributor

Currently one work pool on flow-prd for bl832, default-agent-pool with the queue named bl832, is responsible for handling these deployed functions: new_file_832, prune_data832 and prune_spot832. We should separate this work into a second queue under the work pool called bl832-pruning that takes care pruning tasks. Once they are in separate pools, we can set new_file_832 to be high priority, and prune flows to be low priority.

@davramov davramov changed the title Separate 832 move.py new_file and pruning work pools, set priorities Separate 832 move.py new_file and pruning work queues, set priorities Oct 23, 2024
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

No branches or pull requests

1 participant