feat(utils): distributed reentrant mutex#2664
Open
inkedsquid wants to merge 9 commits into
Open
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
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.



What does this PR do ?
This PR introduces a distributed reentrant mutex utilizing
redlock-universal.Specifically, it:
redlock-universaldependency to handle distributed locking via Redis.withLockinlib/util/mutex2.ts, utilizing Node'sAsyncLocalStorageto keep track of acquired locks within the current execution context, achieving lock reentrancy.lib/core/cache/cacheEngineandlib/service/cache/redisfrom JavaScript to TypeScript for better type safety.How should this be manually tested?
withLockfor the first timeBoyscout
cacheEngineandredisservice files to TypeScript (.ts) to improve the codebase's maintainability and developer experience.es2021for String#ReplaceAll (Sonar Issue)KZLPRD-1241