-
Notifications
You must be signed in to change notification settings - Fork 473
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
Fix slave can't execute publish command #238
Fix slave can't execute publish command #238
Conversation
do we need a new way to implement pub/sub without rely on wal replication ? the current solution write to db cause wal seq to increase (have some feedback from user that it sometimes cause a fullsync when a redis-sentinel failover is trigged, cause by "publish __sentinel:hello" message in new slave) |
ebc4d6d
to
14f049f
Compare
It seems fine that don’t write the WAL when the role was slave. But it would be better to propagate it without writing to WAL. |
I feel ok for current solution. But i have a question, why we persist publish messages? |
We want to use the WAL to help us propagating the publish command like others. |
@Mergifyio backport 1.3 |
(cherry picked from commit 7e09284)
Command
|
@Mergifyio backport 2.0 |
(cherry picked from commit 7e09284)
Command
|
No description provided.