-
Notifications
You must be signed in to change notification settings - Fork 508
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
del key #4487
Comments
meet the same issue. It seems that the root cause is that before master deletes key, it remove spec, so it will not involve index udpate. However, when master deletes key, del is replicated to slave whose spec is still there. So slave involves index update, which is slow. And slave drag down the whole process. Maybe we can do dropindex in slave and then master. It seems it works. |
This issue is stale because it has been open for 60 days with no activity. |
FT.DROPINDEX index DD will delete key as well,but i found this delete process use del instead of unlink which cause redis block。
The text was updated successfully, but these errors were encountered: