-
Notifications
You must be signed in to change notification settings - Fork 4.5k
chore: Use Lettuce client to run clear keys across Redis nodes #36862
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
Merged
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
462db00
Merge pull request #36723 from appsmithorg/release
btsgh 524d400
Merge pull request #36742 from appsmithorg/release
btsgh 485ef8d
chore: Convert redis flush to lettuce commands
nidhi-nair 2e47baf
chore: Convert redis flush to lettuce commands
nidhi-nair File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🛠️ Refactor suggestion
Optimizing Key Scanning and Deletion in Redis
You've effectively encapsulated the Redis key scanning and deletion logic within the
scanForKeysAcrossClustermethod. Here are some suggestions to enhance its performance and reliability:Refine the Scan Pattern: Scanning with a wildcard
"*"can be resource-intensive, especially in a production environment with a large number of keys. If possible, narrow down the pattern to target only the relevant keys that need deletion.Batch Deletion for Efficiency: Deleting keys individually may lead to increased overhead. Batching the keys and performing a bulk delete can improve performance significantly.
Handle Potential Exceptions: It's important to anticipate and handle any exceptions that might occur during the scanning and deletion process to prevent unexpected failures.
Here's how you could modify the method to incorporate these suggestions:
private Mono<Void> scanForKeysAcrossCluster( ReactiveRedisOperations<String, Object> reactiveRedisOperations, String pattern) { return reactiveRedisOperations .execute(connection -> { Flux<ByteBuffer> scanFlux = connection .keyCommands() .scan(ScanOptions.scanOptions() .match(pattern) .count(1000) .build()); - return scanFlux.flatMap(scannedKey -> { - return connection.keyCommands().del(scannedKey); - }) + return scanFlux.buffer(1000) + .flatMap(keys -> connection.keyCommands().del(keys.toArray(new ByteBuffer[0]))) + .onErrorContinue((throwable, obj) -> { + log.error("Error deleting keys: {}", throwable.getMessage()); + }); }) .then(); }buffer(1000): This groups the keys into batches of 1000 before deletion.onErrorContinue: This ensures that if an error occurs during deletion, it logs the error but continues processing the remaining keys.If you'd like further assistance in implementing these changes or have questions about Redis key management, please let me know!
📝 Committable suggestion