-
Notifications
You must be signed in to change notification settings - Fork 579
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
Support the ROLE
command so that Redis.Sentinel is fully supported.
#686
Comments
I have no problem adding the |
The ROLE command has been added to Tile38. It present the basic information that 'INFO replication' would otherwise provide in the format shown here. |
Works! |
@Kilowhisky are you at liberty you share how you setup Tile38 with sentinel? |
@iwpnd I'll post it up once i get it stable. I keep having random problems where the failover causes the AOF to get corrupted or straight up crashes the followers with...
|
@Kilowhisky did you ever get it stable, I'm seeing issues where tile38 keeps showing redis-sentine going from live to not live and causing issues with RESP initial AOF bulk replication. I also had issues with followers crashing. |
Is your feature request related to a problem? Please describe.
Redis Sentinel is a popular way to handle high availability with Redis. It also happens to work with Tile38 except when the Redis client doesn't support the fallback to the
INFO replication
command. This is the case for theStackExchange.Redis
(C#) a Redis client, Unfortunately this client is the defacto standard client for C# based applications.Fortunately the
ROLE
command is a very small command that outputs the same information thatINFO replication
does.See bug with StackExchange.Redis. StackExchange/StackExchange.Redis#2461
Describe the solution you'd like
I would like Tile38 to support the
ROLE
command.Describe alternatives you've considered
I've tried to get the other repo to support the fallback command, but considering the changeover happened LONG ago in the Redis command list they see supporting it as unlikely.
The text was updated successfully, but these errors were encountered: