Standalone scheduler #206
Open
Standalone scheduler #206
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The scheduler can now run as a separate process instead of a background thread in the webapp. This allows the scheduler to be restarted independently in Kubernetes deployments without affecting the webapp. New CLI command: notebooker-cli start-scheduler New webapp flag: --scheduler-management-only When using the standalone scheduler, the webapp should be started with --scheduler-management-only so it can manage jobs without executing them.
- Use scheduler.start(paused=True) to prevent jobs firing before pause - Fix _gen_all_templates to skip empty folders (was showing folder names) - Fix test ordering assertion for templates endpoint - Apply black and prettier formatting
🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The current implementation of the scheduler is running as a background thread in the webapp. This change allows us to instead deploy the scheduler as a separate process for production use-cases such that it can be given the correct resources, lifecycled, etc.