-
Notifications
You must be signed in to change notification settings - Fork 132
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 Concurrency entity for worker #1405
Open
shijiesheng
wants to merge
11
commits into
cadence-workflow:master
Choose a base branch
from
shijiesheng:dynamicparams
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from 1 commit
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
abf6b28
add DynamicParams for worker
shijiesheng 9010a8c
remove unwanted comment
shijiesheng 4ee4500
fix initialization
shijiesheng f065c10
propagate context
shijiesheng a982c04
fix leaked goroutine
shijiesheng b99b8ce
address comments and add unit tests
shijiesheng dc99021
rename
shijiesheng 5bcc55b
lint
shijiesheng f08bd7c
fix flaky unit test
shijiesheng e6d7036
better testing
shijiesheng f453fb3
fix potential blocking
shijiesheng File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
This file contains 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
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.
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.
found a race condition of channel sending. Adding a wait time would be more reliable
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.
hmm :\ unfortunately this means that if processing is delayed by 10ms it will block the chan-reader forever. that's not too unlikely with big CPU spikes, and definitely not impossible.
tbh I think that might rule this impl out entirely. though I think it's possible to build a
AcquireChan(...) (<-chan struct{}, cancel func())
that doesn't have this issue, and that might be worth doing.or we might have to embrace the atomic-like behavior around this and add retries to
(*baseWorker).runPoller
/ anything usingAcquireChan
. that wouldn't be a fatal constraint afaict, though it's not ideal.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.
if we expect chan-reader to always consume from the returned
ch
unless ctx is canceled then we can replace this goroutine implementation withThere 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.
fixed through Taylan's suggestion. It should be safe now.