[EventCounters] fix deadlock - #1260
Merged
Merged
Conversation
besseb05
approved these changes
Jul 5, 2023
besseb05
left a comment
There was a problem hiding this comment.
lgtm - although I am not familiar with the codebase
utpilla
reviewed
Jul 7, 2023
reyang
approved these changes
Jul 10, 2023
utpilla
approved these changes
Jul 10, 2023
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
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.
Mitigates #1024.
Changes
Below is an example of when the deadlock can occur:
EventCountersMetricspreInitEventSourcespreInitEventSourcesobject by thread 1EventSourcesAND enable themEventSourceby thread 1EventSourceAgot enabled by thread 1OnEventWrittencallback fired on receiving an eventEventCountersInstrumentationEventSourcegot lazy-initEventSourceby thread 2OnEventSourceCreatedcallback firedpreInitEventSoucespreInitEventSoucesby thread 2Discussion
preInitEventSourceswere added in this PR to address the issue -"As OnEventSourceCreated can run before the constructor is done, you can run into a situation where you fail to enable an EventSource instance."
@MihaZupan: Instead of the current locking mechanism, Is it possible in
OnEventSourceCreated, we use Spinlock to wait untilthis.optionswas set to ensure thatOnEventSourceCreatedwill be triggered only after thectorgot executed? Too hacky?For significant contributions please make sure you have completed the following items:
CHANGELOG.mdupdated for non-trivial changes