Feat add redis distributed locking mechanism #911
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
SalmaElsoly
force-pushed
the
master_distributed_locks
branch
3 times, most recently
from
d0623bd to
ec85e80
Compare
xmonader
reviewed
Nov 30, 2025
xmonader
reviewed
Nov 30, 2025
SalmaElsoly
force-pushed
the
master_distributed_locks
branch
from
ec85e80 to
2ec13a8
Compare
SalmaElsoly
force-pushed
the
master_distributed_locks
branch
from
98ef89d to
2884a17
Compare
SalmaElsoly
force-pushed
the
master_distributed_locks
branch
from
2884a17 to
3da4962
Compare
SalmaElsoly
force-pushed
the
master_distributed_locks
branch
from
3da4962 to
6c8bbc8
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
This pull request introduces a distributed locking mechanism for nodes using Redis, to keep node resources synchronized
Changes
DistributedLocksinterface and a Redis-based implementation (RedisLocker) for managing node and workflow locks, including methods to acquire, release, and query locks.NodeHandlerandDeploymentHandlerto use the distributed locking mechanism. Now, before performing operations like reserving a node, deploying a cluster, or adding a node, the handlers attempt to acquire locks on the relevant nodes. If a node is already locked, the request will be rejected with a conflict error.Related Issues
#872
Checklist