-
Notifications
You must be signed in to change notification settings - Fork 883
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
replicating redis 7.0.2 cause a sync loop #1680
Comments
looks like that this field is set by redis to "0" for a regular (non aof) case: https://github.com/redis/redis/blob/1b6bdff48dcc333affab02b945821eb865529de2/src/rdb.c#L3156 |
So it appears we aren't doing that :) Do you think we should? |
seems like we should :) |
Oops, we ARE correctly ignoring this field. When running locally I get the same messages:
But no reconnection loop. @cecchigl, would you mind posting your redis configuration check the redis server's logs? To me it looks like the connection might have been closed from redis' side for some reason. |
If an empty buffer is passed to the socket Recv function - it returns error 103. Even if we returned success, this would lead to the endless loop since the parser requires more data to parse the load. Fixes #1680 Signed-off-by: Roman Gershman <roman@dragonflydb.io>
Describe the bug
Setting dragonfly as a replicaof a redis 7.0.2 instance cause a sync loop
To Reproduce
Steps to reproduce the behavior:
replicaof host port
(redis address)Expected behavior
Full sync with redis db
Environment (please complete the following information):
Additional context
Dragonfly logs:
The text was updated successfully, but these errors were encountered: