Skip to content

When SlotNotCoveredError is raised, the cluster topology should be reinitialized as part of error handling and retrying of the commands. #3621

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 2 commits into from
Apr 29, 2025

Conversation

petyaslavova
Copy link
Collaborator

Pull Request check-list

Please make sure to review and check all of these items:

  • Do tests and lints pass with this change?
  • Do the CI tests pass with this change (enable it first in your forked repo and wait for the github action build to finish)?
  • Is the new or changed code fully tested?
  • Is a documentation update included (if this change modifies existing APIs, or introduces new ones)?
  • Is there an example added to the examples folder (if applicable)?
  • Was the change added to CHANGES file?

NOTE: these things are not required to open a PR and can be done
afterwards / while the PR is open.

Description of change

Fixes issue #3620

When we are handling different errors, we run cluster reinitialization that calls CLUSTER SLOTS.
Sometimes the cluster slots temporarily might not be fully covered and if we try to execute a command against key from the missing slots we receive SlotNotCoveredError.
The problem is that after this error appears we don't try to reinitialize again the slots and the Cluster client can't heal itself.

With this change I'm adding error handling for the SlotNotCoveredError, the same way we handle ClusterDownErrors - try to extract the slots coverage after a little sleep.

…initialized as part of error handling and retrying of the commands.
@petyaslavova petyaslavova added the bug Bug label Apr 28, 2025
@petyaslavova petyaslavova merged commit a4df6b2 into master Apr 29, 2025
37 checks passed
@petyaslavova petyaslavova deleted the ps_fix_cluster_client_on_clot_not_covered branch April 29, 2025 13:48
petyaslavova added a commit that referenced this pull request Apr 29, 2025
…initialized as part of error handling and retrying of the commands. (#3621)
petyaslavova added a commit that referenced this pull request Apr 29, 2025
…initialized as part of error handling and retrying of the commands. (#3621)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Bug
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants