-
Notifications
You must be signed in to change notification settings - Fork 24.4k
Add tests to make sure that relative EXPIRE is propagated to replicas #8357
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
Conversation
|
Hi @oranagra Actually, I ever wanted to always propagate absolute expire commands, but Salvatore said But could we have a way to only propagate absolute expire commands? For this big idea #4357 my team already implemented |
Co-authored-by: Itamar Haber <itamar@redislabs.com>
|
i'm merging this for now to pin the current state. we can open that for discussion after (either here of in a new issue) |
…redis#8357) This commit adds tests to make sure that relative and absolute expire commands are propagated as is to replicas and stop any future attempt to change that without a proper discussion. see redis#8327 and redis#5171 Additionally it slightly improve the AOF test that tests the opposite (always propagating absolute times), by covering more commands, and shaving 2 seconds from the test time.
This commit adds tests to make sure that relative and absolute expire commands
are propagated as is to replicas and stop any future attempt to change that without
a proper discussion. see #8327 and #5171
Additionally it slightly improve the AOF test that tests the opposite (always
propagating absolute times), by covering more commands, and shaving 2
seconds from the test time.