-
Notifications
You must be signed in to change notification settings - Fork 123
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
fix: batched reassign and requeue #701
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
||
stepRunId := sqlchelpers.UUIDToStr(stepRunCp.StepRun.ID) | ||
// wrap in func to avoid leaking spans |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
im not sure if this is needed
g.Go(func() error { | ||
ctx, span := telemetry.NewSpan(ctx, "handle-step-run-requeue-step-run") | ||
defer span.End() | ||
scheduleCtx, cancel := context.WithTimeout(ctx, 1*time.Second) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
not sure about this. it should be fine considering requeueAfter is set to now + 4s and initial context takes up 1 second and sets sr into a state so they should not be re-re-assigned. but writing 100 sr updates maybe shouldnt take more than 1s?
Description
Addresses db load under high throughput
Type of change
What's Changed