Fix Settings.InjectTopLevelFallback race condition
#7721
Merged
Conversation
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
Arkatufus
commented
Jul 2, 2025
Comment on lines
+52
to
+58
| while(true) | ||
| { | ||
| var oldConfig = _fallbackConfig.Value; | ||
| var newConfig = config.SafeWithFallback(oldConfig); | ||
| if (_fallbackConfig.CompareAndSet(oldConfig, newConfig)) | ||
| break; | ||
| } |
Contributor
Author
There was a problem hiding this comment.
Fix: Do not assign value to naked field directly, this can cause race condition if multiple Akka extensions running in multiple threads tries to start at the same time.
Scenario:
- Time 0
- Extension "A" reads
_fallbackConfigintoconfigA - Extension "B" reads
_fallbackConfigintoconfigB
- Extension "A" reads
- Time 1
- Extension "A" injects "akka.cluster.tools.singleton" into
configA - Extension "B" injects "akka.persistence.sql" into
configB
- Extension "A" injects "akka.cluster.tools.singleton" into
- Time 2
- Extension "A" writes
configAinto_fallbackConfig
- Extension "A" writes
- Time 3
- Extension "B" writes
configBinto_fallbackConfig
- Extension "B" writes
- Time 4
- Extension "A" reads "akka.cluster.tools.singleton" from
Settings.Config, getsNullReferenceExceptionbecause it got clobbered by Extension "B"
- Extension "A" reads "akka.cluster.tools.singleton" from
Aaronontheweb
approved these changes
Jul 2, 2025
Member
Aaronontheweb
left a comment
Aaronontheweb
left a comment
There was a problem hiding this comment.
LGTM - that was simple. Let's see how the testing system does.
| private readonly Config _userConfig; | ||
| //internal static readonly Config AkkaDllConfig = ConfigurationFactory.FromResource<Settings>("Akka.Configuration.Pigeon.conf"); | ||
| private Config _fallbackConfig; | ||
| private readonly AtomicReference<Config> _fallbackConfig; |
Member
There was a problem hiding this comment.
yeah, this is a much simpler fix than what I was imagining
Comment on lines
+52
to
+58
| while(true) | ||
| { | ||
| var oldConfig = _fallbackConfig.Value; | ||
| var newConfig = config.SafeWithFallback(oldConfig); | ||
| if (_fallbackConfig.CompareAndSet(oldConfig, newConfig)) | ||
| break; | ||
| } |
This was referenced Jul 7, 2025
This was referenced Jul 25, 2025
This was referenced Aug 4, 2025
This was referenced Oct 7, 2025
This was referenced Oct 20, 2025
This was referenced Oct 27, 2025
This was referenced Nov 6, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Fixes #7426
Changes
AtomicReference<T>to enforce thread safety