sentinel monitor kvrocks

Aperta
  • Qualcosa non va?
#3,267 4 commenti 0 reazioni 1 assegnatario Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@aviralgarg05 ci sta già lavorando.

Dal 10/4/2026.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

bug
Search before asking
  • I had searched in the issues and found no similar issues.
Version

My Kvrocks instance (kvrockstest-001) uses a non-cluster mode master-slave architecture. kvrocks version 2.14.0。sentinel version 5.0.14。

During testing with Sentinel supervision, I discovered that after executing the monitor add command on all Sentinel nodes, the Sentinel info display showed abnormalities - it indicated only 1 Sentinel instance and failed to recognize the slave nodes of this Kvrocks instance. The ports between Sentinel nodes and between Sentinel and Kvrocks nodes are mutually accessible.

The issue can be resolved by either executing sentinel reset kvrockstest-001 or restarting the Sentinel service。

Commands to add supervision:

sentinel monitor kvrockstest-001 192.168.56.103 6666 2
sentinel set kvrockstest-001 down-after-milliseconds 20000
sentinel set kvrockstest-001 failover-timeout 5000
sentinel set kvrockstest-001 parallel-syncs 1
sentinel set kvrockstest-001 auth-pass 123456

sentinel info信息：
127.0.0.1:27379> info Sentinel

Sentinel

sentinel_masters:1
sentinel_tilt:0
sentinel_running_scripts:0
sentinel_scripts_queue_length:0
sentinel_simulate_failure_flags:0
master0:name=kvrockstest-001,status=sdown,address=192.168.56.103:6666,slaves=0,sentinels=1

sentinel service log msg：
36204:X 20 Nov 2025 17:35:57.673 # +monitor master kvrockstest-001 192.168.56.103 6666 quorum 2
36204:X 20 Nov 2025 17:35:57.680 # +set master kvrockstest-001 192.168.56.103 6666 down-after-milliseconds 20000
36204:X 20 Nov 2025 17:35:57.689 # +set master kvrockstest-001 192.168.56.103 6666 failover-timeout 5000
36204:X 20 Nov 2025 17:35:57.704 # +set master kvrockstest-001 192.168.56.103 6666 parallel-syncs 1
36204:X 20 Nov 2025 17:35:58.506 # +set master kvrockstest-001 192.168.56.103 6666 auth-pass 123456
36204:X 20 Nov 2025 17:36:17.688 # +sdown master kvrockstest-001 192.168.56.103 6666
36204:X 20 Nov 2025 17:37:42.673 - Accepted 192.168.56.105:44340
36204:X 20 Nov 2025 17:37:44.835 - Client closed connection
36204:X 20 Nov 2025 17:38:53.220 * +sentinel sentinel efb25b56bb7d7083bedcc9799f8d697493d37698 192.168.56.105 27379 @ kvrockstest-001 192.168.56.103 6666
36204:X 20 Nov 2025 17:38:55.326 - Accepted 192.168.56.105:47618
36204:X 20 Nov 2025 17:38:56.957 # +reset-master master kvrockstest-001 192.168.56.103 6666
36204:X 20 Nov 2025 17:38:56.962 * +slave slave 192.168.56.105:6666 192.168.56.105 6666 @ kvrockstest-001 192.168.56.103 6666
36204:X 20 Nov 2025 17:38:57.318 * +sentinel sentinel efb25b56bb7d7083bedcc9799f8d697493d37698 192.168.56.105 27379 @ kvrockstest-001 192.168.56.103 6666

Minimal reproduce step

none

What did you expect to see?

all

What did you see instead?

none

Anything Else?

none

Are you willing to submit a PR?
  • I'm willing to submit a PR!
Lingua principale
C++
Stelle
4.5k
Fork
686
Merge medio
2g 19h
PR unite (30g)
37

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

  • Include un Dockerfile o un file Docker Compose
  • Nessun modello di pull request
  • Nessuna guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di apache/kvrocks

Tutte le issue di apache/kvrocks

Issue simili

Altre issue su C++

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.