Open charles-horel opened 4 months ago
Hi, I have the same question, from what I see, the Redis instance is not created, just sentinel. Hope some information will be provided.
@charles-horel I explored the repository issues/discussion threads and found out that it is required to deploy redis-replication as well.
replication + sentinel
ot-operators redis-operator-67bcf649cb-5gwrb 1/1 Running 0 3d1h
ot-operators redis-replication-0 1/1 Running 0 3m6s
ot-operators redis-replication-1 1/1 Running 0 2m57s
ot-operators redis-replication-2 1/1 Running 0 2m48s
ot-operators redis-sentinel-sentinel-2 1/1 Running 0 87s
ot-operators redis-sentinel-sentinel-1 1/1 Running 0 53s
ot-operators redis-sentinel-sentinel-0 1/1 Running 0 18s
Logs from a sentinel pod
7:X 26 Apr 2024 12:52:23.057 * Running mode=sentinel, port=26379.
7:X 26 Apr 2024 12:52:23.062 * Sentinel new configuration saved on disk
7:X 26 Apr 2024 12:52:23.062 * Sentinel ID is 5992766d4aa736de7aea2b701c60faff194b28be
7:X 26 Apr 2024 12:52:23.062 # +monitor master myMaster 10.42.1.149 6379 quorum 2
7:X 26 Apr 2024 12:52:23.064 * +slave slave 10.42.2.34:6379 10.42.2.34 6379 @ myMaster 10.42.1.149 6379
7:X 26 Apr 2024 12:52:23.069 * Sentinel new configuration saved on disk
7:X 26 Apr 2024 12:52:23.069 * +slave slave 10.42.0.13:6379 10.42.0.13 6379 @ myMaster 10.42.1.149 6379
7:X 26 Apr 2024 12:52:23.073 * Sentinel new configuration saved on disk
7:X 26 Apr 2024 12:52:59.533 * +sentinel sentinel 0e90f8b2c2d4179b31dc36c4d401fb76463f4220 10.42.2.35 26379 @ myMaster 10.42.1.149 6379
7:X 26 Apr 2024 12:52:59.539 * Sentinel new configuration saved on disk
7:X 26 Apr 2024 12:53:34.457 * +sentinel sentinel ad0de1c35e240ec546511971cf91ae3b5666720a 10.42.1.150 26379 @ myMaster 10.42.1.149 6379
7:X 26 Apr 2024 12:53:34.463 * Sentinel new configuration saved on disk
We are trying to deploy an instance of the redis-sentinel chart. We were initially under the impression that the chart would build sentinel pods which also contain/manage standalone redis nodes.
Helm values (deploying latest version of sentinel chart)
When the sentinel pods start up, we can see hints in the logs that a redis server is starting:
However we cannot use a sentinel client to connect to a working redis instance. We will get 'No master found for 'myMaster' trying to use a python redis.Sentinel object. If I connect to the sentinel CLI from inside of the pod, however, and tell it to give me the master, it tells me it's 0.0.0.0/6379:
But there are no services or ports exposed on the sentinel pods on port 6379. Inside of the sentinel container, nothing is bound to this port, and there is no process running other than sentinel:
It almost looks like I need to deploy standalone redis instances that get leveraged by Sentinel. Can someone confirm to me whether or not this is the case? If it is, would I deploy 3x standalones or would I use a cluster of 3 masters?