keva-dev / keva-dev/keva

[Sentinel/Keva] Pub/sub for Sentinel

Open
#24 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
109
Forks
11
PR merge metrics
No merged PRs in 30d

Description

Sentinels that monitor the same Redis instance discovers each other by subscribing to the channel "__sentinel__:hello" of that Redis instance, and publish its own information to this channel each 1 second, so that other sentinels know about it.

Keva does not have Pub/sub yet, but Sentinels need an intermediary to communicate.

At first, i think we can workaround by including sentinels information in Redis INFO command result, and sentinel can get that when it periodically make call to the instance.
And another internal endpoint for Sentinels to introduce itself to Redis instances.

Contributor guide

Open the contributing guide

Research direction

No files or tests are identified. Start by tracing the existing Redis INFO command and Sentinel integration, then evaluate the proposed Sentinel information endpoint and INFO-based discovery; done means Sentinels monitoring the same instance can introduce themselves and discover one another without native pub/sub.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, redis
Domain
backend, distributed-systems
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.