DistributedLock icon indicating copy to clipboard operation
DistributedLock copied to clipboard

A .NET library for distributed synchronization

Results 57 DistributedLock issues
Sort by recently updated
recently updated
newest added

In https://github.com/madelson/DistributedLock/issues/38, we consider a 2-layer locking approach where an in-memory lock must be taken before making any calls to the distributed layer. The idea is to reduce impact on...

enhancement

Second time I've run into a particular issue. A granted lock is never released after over a day. Using the following code: ``` var myLock = new SqlDistributedLock($"ProductsJob_, "ConnectionString"); using...

Right now we have 2 constructors: ``` public DedicatedConnectionOrTransactionDbDistributedLock(string name, Func externalConnectionFactory) public DedicatedConnectionOrTransactionDbDistributedLock( string name, Func connectionFactory, bool useTransaction, TimeoutValue keepaliveCadence) ``` Both are a bit confusing. The first...

cleanup

https://github.com/dotnet/SqlClient/issues/727 can cause issues for people using DistributedLock 2.0 in .NET framework executables. Might be good to call this out explicitly in the docs to head off questions. Also could...

enhancement

``` public DedicatedConnectionOrTransactionDbDistributedLock( string name, Func connectionFactory, bool useTransaction, TimeoutValue keepaliveCadence) ``` This constructor is only referenced from Core itself, so no need to make it visible to the implementation...

cleanup

Once https://github.com/dotnet/SqlClient/issues/971 is fixed, we should make that a minimum version requirement for our next release since it is an issue people might run into with long-lived connections (see https://github.com/madelson/DistributedLock/issues/83).

cleanup

Hi! I'm using Azure SQL Server and my app do not use login and password in connection strings. I'm using this approach for secure connection https://docs.microsoft.com/en-us/azure/app-service/app-service-web-tutorial-connect-msi#modify-aspnet-core So to make it...

enhancement

Probably we can phase out the "opportunistic" flag and instead just make the same call first on an existing lock and then on a new lock. Internally, we fork on...

cleanup