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 lock when configuration is null #2780

Merged
merged 1 commit into from
Aug 15, 2024
Merged

Conversation

brentschmaltz
Copy link
Member

Metadata is now updated on a background Task.
Previously updating was behind a SlimLock on every update to the metadata endpoint which resulted in a blocking call when RequestRefresh or AutomaticRefresh were called.

The lock is applied only when configuration has not been obtained, this stops the case when a number of threads startup and each thread would hit the metadata endpoint.

@brentschmaltz brentschmaltz requested a review from a team as a code owner August 13, 2024 17:46
@brentschmaltz brentschmaltz force-pushed the brentsch/RemoveSlimLock branch from efa0143 to cfa85a8 Compare August 15, 2024 16:31
@brentschmaltz brentschmaltz merged commit eb4df8f into dev Aug 15, 2024
5 of 6 checks passed
@keegan-caruso keegan-caruso added this to the 8.0.2 milestone Aug 19, 2024
@brentschmaltz brentschmaltz deleted the brentsch/RemoveSlimLock branch October 23, 2024 21:54
keegan-caruso pushed a commit that referenced this pull request Jan 10, 2025
Further reverting the change to RequestRefresh from #2780
This is still too much of a behavioral change. RequestRefresh goes back
to its historical function, signalling that the next call to
GetConfigurationAsync should request data. This is incorporated with
the background thread change to instead do the request as a blocking
operation if from a RequestRefresh

Part of #3082
keegan-caruso added a commit that referenced this pull request Jan 10, 2025
* RequestRefresh back to a signal

Further reverting the change to RequestRefresh from #2780
This is still too much of a behavioral change. RequestRefresh goes back
to its historical function, signalling that the next call to
GetConfigurationAsync should request data. This is incorporated with
the background thread change to instead do the request as a blocking
operation if from a RequestRefresh

Part of #3082

* Add time based testing to ConfigurationManagerTests
through FakeTimeProvider
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.

4 participants