-
Notifications
You must be signed in to change notification settings - Fork 559
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
Compatibility Issue with Medallion.Threading.Redis and Garnet #1098
Comments
@kevin-montrose, I tested it locally with your branch and it seems to resolve the issue. |
I have tested it on main branch and it still works locally (Mac OS)! it seems that the issue appears when I run the server on a container. |
I wouldn't close the issue because the issue persists when running garnet on a container. |
Once the container for latest main auto-releases in at most an hour, can you retry? |
I still have the issue with latest version running on a container.
|
can you confirm you used |
Worth noting I cannot reproduce this on
And a linqpad script of void Main()
{
var config = ConfigurationOptions.Parse("localhost:8000");
config.SocketManager = SocketManager.ThreadPool;
var connection = ConnectionMultiplexer.Connect(config, Console.Out);
var db = connection.GetDatabase();
var dLock = new RedisDistributedSynchronizationProvider(db);
var aLock = dLock.AcquireLock("123_lock");
Console.WriteLine("Lock acquired");
aLock.Dispose();
Console.WriteLine("Lock released");
} Produces:
|
I'm running it on another device and still have the same issue Screen.Recording.2025-03-19.at.20.51.47.mp4 |
Can you retry with server running on |
|
Not seeing anything of note in the logs at this point to make progress on this. |
Describe the bug
We attempted to use Garnet as a Redis replacement for our distributed locking mechanism using Medallion.Threading.Redis (version 1.0.3). However, we encountered an issue when trying to acquire a lock.
The same code works fine when using Redis, but fails when using Garnet.
NuGet Packages Used:
Observed Behavior (Error Logs)
Steps to reproduce the bug
Garnet Configuration
Client
Garnet Version
The text was updated successfully, but these errors were encountered: