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

Introduce separate slot supplier for session activities #1736

Merged
merged 3 commits into from
Dec 2, 2024

Conversation

Sushisource
Copy link
Member

What was changed

There's now a separate slot supplier for session activities. Turns out this was also broken before in a different way, since previous to the slot suppliers change, session activity workers would have their own independent max concurrent, equal to the normal activity setting. Hence users using sessions could easily exceed the max number they thought they set.

Why?

Without it, pollers for the session TQ can starve the normal activity TQ of slots

Checklist

  1. Closes Session worker delays with single activity limit after Tuner introduction #1732

  2. How was this tested:
    Added integ test

  3. Any docs updates needed?
    Need to add some Go specific changes to docs on slot suppliers

@Sushisource Sushisource requested a review from a team as a code owner December 2, 2024 20:17
@Sushisource Sushisource merged commit 2c6bc1d into master Dec 2, 2024
14 checks passed
@Sushisource Sushisource deleted the session-slot-supplier branch December 2, 2024 22:23
ReyOrtiz pushed a commit to ReyOrtiz/temporal-sdk-go that referenced this pull request Dec 5, 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

Successfully merging this pull request may close these issues.

Session worker delays with single activity limit after Tuner introduction
3 participants