-
We can practically have any usage, sans the locking. W/O Locking it is impossible to protect any resource. This resource can be anything that gets shared between two processors running on two separate…
-
### Describe the bug
In the timed outbox sweeper we use a Locking provider
``` c#
var lockId = _distributedLock.ObtainLockAsync(LockingResourceName, CancellationToken.None).Result;
…
-
We're currently using Redis SETNX to prevent an op from being evented more than once.
Technically during a Redis fail-over, more than one process may receive the lock for an op.
A solution is de…
-
[Link](https://martin.kleppmann.com/2016/02/08/how-to-do-distributed-locking.html)
-
**What happened**:
Using an asynchronous `dask.distributed.Client` both the asynchronous and synchronous context managers are asynchronous. Producing a `coroutine 'PooledRPCCall.__getattr__..sen…
-
### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar feature requirement.
### Description
As we now su…
-
version: v1.0.47
```go
const fallbackSETPXVersion = "6.2.0"
type wrapLocker struct {
v ConfInterface
rueidislock.Locker
}
func (w *wrapLocker) wrap(ctx context.Context, name string,…
-
We would like to ensure that hosts in HA clusters cannot run components at the same time, an obvious solution to this would to be to use a distributed lock manager such as Zookeeper or etcd. This is t…
-
Description:
We need to enhance our ServiceLevelObjective (SLO) Custom Resource Definition (CRD) to better support multi-cluster deployments with a centralized monitoring solution. The current impl…
-
Hello,
I'm facing an issue when calling `.compute` in distributed multi-node setting.
The symptoms are the same as in huggingface/datasets#4420 , however I'm not sure the cause is the same (the co…