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.
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.