We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
After errors during cluster scaling one of cluster's nodes became inconsistent. Some keys of one particular slot have remained on the old shard.
We have restored all the data, but keys are still on the wrong shard. SCAN returns them, but any other command returns MOVED error:
redis-cli -h 10.222.122.7 10.222.122.7:6379> scan 0 match pwe_userid:9fd386a4-94f9-4732-b2a7-ad2442d4f252 count 100000 1) "3505504" 2) 1) "pwe_userid:9fd386a4-94f9-4732-b2a7-ad2442d4f252" 10.222.122.7:6379> cluster keyslot pwe_userid:9fd386a4-94f9-4732-b2a7-ad2442d4f252 (integer) 6456 10.222.122.7:6379> cluster slots ... 4) 1) (integer) 8192 2) (integer) 10922 3) 1) "10.222.122.7" 2) (integer) 6379 3) "c4a81e6707c4bd0f3534df81803f0307ca2a18d6" 4) (empty array) 4) 1) "10.222.145.28" 2) (integer) 6379 3) "d8089ddc9970fcc9d16d85fb419fab9e2715e0c3" 4) (empty array) ... 10.222.122.7:6379> del pwe_userid:9fd386a4-94f9-4732-b2a7-ad2442d4f252 (error) MOVED 6456 10.222.60.143:6379
Is there any way to just delete these keys without heavy migration procedures and without removing the node from the cluster?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
After errors during cluster scaling one of cluster's nodes became inconsistent. Some keys of one particular slot have remained on the old shard.
We have restored all the data, but keys are still on the wrong shard. SCAN returns them, but any other command returns MOVED error:
Is there any way to just delete these keys without heavy migration procedures and without removing the node from the cluster?
The text was updated successfully, but these errors were encountered: