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

Add an "initial_jitter_seconds" field to DagsterDaemon #21789

Merged
merged 1 commit into from May 16, 2024
Merged

Conversation

gibsondan
Copy link
Member

Summary:
Allows daemons to be configured in such a way that they do not all hammer the DB simultaneously on startup

Test Plan: See corresponding internal PR

Summary & Motivation

How I Tested These Changes

self.interval_seconds = check.numeric_param(interval_seconds, "interval_seconds")
self.jitter_seconds = jitter_seconds
self.interval_jitter_seconds = interval_jitter_seconds
self.initial_jitter_seconds = initial_jitter_seconds
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

startup_jitter_seconds? Just because interval and initial read so similarly when skimming.

Summary:
Allows daemons to be configured in such a way that they do not all hammer the DB simultaneously on startup

Test Plan: See corresponding internal PR
@gibsondan gibsondan merged commit ff0cadf into master May 16, 2024
1 check passed
@gibsondan gibsondan deleted the addinitial branch May 16, 2024 20:28
nikomancy pushed a commit that referenced this pull request May 22, 2024
Summary:
Allows daemons to be configured in such a way that they do not all
hammer the DB simultaneously on startup

Test Plan: See corresponding internal PR

## Summary & Motivation

## How I Tested These Changes
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.

None yet

2 participants