microsoft/garnet

Basic sentinel high availability with automatic failover is required

Open

#927 opened on Jan 18, 2025

View on GitHub
 (1 comment) (0 reactions) (0 assignees)C# (11,827 stars) (660 forks)batch import
enhancementhelp wanted

Description

Feature request type

enhancement

Is your feature request related to a problem? Please describe

Apart from clustering and data sharding replication, basic Sentinel replication with failover is needed immediately. Sentinel is easy to configure and maintain, and it also supports multiple databases.

Describe the solution you'd like

Apart from clustering and data sharding replication, basic Sentinel replication with failover is needed immediately. Sentinel is easy to configure and maintain, and it also supports multiple databases. Like redis please provide sentinel feature.

Describe alternatives you've considered

Additional context

No response

Contributor guide

Tech stack
csharp
Domain
backenddatabase
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
5
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
C#distributed systemsreplication concepts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
15
Research direction
Examine Garnet's existing replication and cluster sharding code in the repository (likely under src/). Study the Redis Sentinel protocol and failover logic. Look for any prior discussions in issues or PRs about high availability. Propose a design document outlining the sentinel architecture with automatic failover before implementation.