-
-
Notifications
You must be signed in to change notification settings - Fork 15
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
Never ending loop "Competing reserved resource accessed via runSync" #360
Comments
Hey! This is due to the same issue you reported before (#358). In this case, a read (maybe compaction) is accessing an I think if you made all your configurations use Hope this resolves the problem. |
After giving this some more thought, I'm afraid it might not fully resolve the problem you are having. This will be fully resolved in issue #318. |
@simerplaha yeah it is not resolving the issue It completly stagnate here
|
My use case is very easy, I'm using off-heap map to store some counters. Read and write is single threaded.
Very frequently my application is not functioning correctly because it cannot acces collection - the only sign that something is not working correctly is following log.
This counter goes to the moon
3843425
Is there any way to set some configuration parameters to avoid such situations - maybe by disabling compaction etc
Because my use case is very simple - the only compeeting process could be some swaydb -internal compaction etc.
Bellow you can find the config that I'm currently using.
The text was updated successfully, but these errors were encountered: