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# (660 forks)batch import
enhancementhelp wanted

Repository metrics

Stars
 (11,827 stars)
PR merge metrics
 (Avg merge 5d 16h) (55 merged PRs in 30d)

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

Research direction
Study the existing replication and cluster sharding code in Garnet, then design and implement a Sentinel like component for automatic failover. Start by understanding how Redis Sentinel works and map it to Garnet's architecture.
Tech stack
csharpredis
Domain
backenddatabaseinfrastructure
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
C#RedisDistributed Systems
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40