Open iamNoah1 opened 3 months ago
wkd-woo
commented
3 months ago I think 'clusterSize' should be the same value as 'leader.replicas' + 'follower.replicas'.
'RedisCluster' doesn't mean "a set" of Redis cluster. This means one member, as a 'Custom Resource' in itself called the 'RedisCluster'.
Try clusterSize=6.
and as you already know, redis cluster 'one set' configuration requires at least three master leaders.
iamNoah1
commented
3 months ago Thanks for the reply @wkd-woo. I cannot confirm that clusterSize is equal to leader.replicas + follower.replicas. It does not matter if I configure it to 1, 3 or 6, it always remains 3 leaders and 3 followers.
According to different information sources like this it should work like I expected which is when I set ClusterSize to 5 having 5 leader and 5 follower nodes. But it does not :) ...
wkd-woo
commented
3 months ago @iamNoah1 Oh, I understand your situation. I've been wandering around with the same problem before.
I'll give you the test manifest I'm using. I recommend override the .yaml file with '-f' rather than 'set'
helm install redis-cluster helm/chart/redis-cluster -f values.yaml
---
redisCluster:
name: ""
clusterSize: 6
clusterVersion: v7
persistenceEnabled: false
image: quay.io/opstree/redis
tag: v7.0.12
imagePullPolicy: IfNotPresent
imagePullSecrets: {}
redisSecret:
secretName: ""
secretKey: ""
resources:
limits:
cpu: 101m
memory: 512Mi
leader:
replicas: 3
serviceType: ClusterIP
affinity:
tolerations: []
nodeSelector:
kubernetes.io/os: linux
dbservice: redis
topology: cluster
securityContext: {}
pdb:
enabled: false
maxUnavailable: 1
minAvailable: 1
follower:
replicas: 3
serviceType: ClusterIP
affinity:
tolerations: []
nodeSelector:
dbservice: redis
topology: cluster
securityContext: {}
pdb:
enabled: false
maxUnavailable: 1
minAvailable: 1
labels:
topology: cluster
dbservice: redis
externalConfig:
enabled: true
data: |
#### YOUR CONFIGURATION FOR REDIS ####
externalService:
enabled: true
# annotations:
# foo: bar
serviceType: NodePort
port: 6379
serviceMonitor:
enabled: false
interval: 30s
scrapeTimeout: 10s
namespace: monitoring
redisExporter:
enabled: true
image: quay.io/opstree/redis-exporter
tag: v1.44.0
imagePullPolicy: IfNotPresent
resources:
limits:
cpu: 100m
memory: 128Mi
env: []
sidecars:
name: ""
image: ""
imagePullPolicy: "IfNotPresent"
resources:
limits:
cpu: "100m"
memory: "128Mi"
requests:
cpu: "50m"
memory: "64Mi"
env: {}
initContainer:
enabled: false
image: ""
imagePullPolicy: "IfNotPresent"
resources: {}
env: []
command: []
args: []
priorityClassName: ""
storageSpec:
volumeClaimTemplate:
spec:
# storageClassName: local-storage
storageClassName: csi-cinder-sc-delete
accessModes: ["ReadWriteOnce"]
resources:
requests:
storage: 10Gi
# selector:
# matchLabels:
# dbservice: redis
# topology: cluster
nodeConfVolume: true
nodeConfVolumeClaimTemplate:
spec:
# storageClassName: local-storage
storageClassName: csi-cinder-sc-delete
accessModes: ["ReadWriteOnce"]
resources:
requests:
storage: 10Gi
# selector:
# matchLabels:
# dbservice: redis
# topology: cluster
podSecurityContext:
runAsUser: 1000
fsGroup: 1000
TLS:
ca: ca.key
cert: tls.crt
key: tls.key
secret:
secretName: ""
acl:
secret:
secretName: ""
#env:
serviceAccountName: "redis-operator"
What version of redis operator are you using?
redis-operator version: redis-operator-0.15.9
Does this issue reproduce with the latest release? This is the latest helm chart I could get
What operating system and processor architecture are you using (
kubectl version)?kubectl versionOutput$ kubectl version Client Version: version.Info{Major:"1", Minor:"27", GitVersion:"v1.27.2", GitCommit:"7f6f68fdabc4df88cfea2dcf9a19b2b830f1e647", GitTreeState:"clean", BuildDate:"2023-05-17T14:20:07Z", GoVersion:"go1.20.4", Compiler:"gc", Platform:"darwin/arm64"} Kustomize Version: v5.0.1 Server Version: version.Info{Major:"1", Minor:"27", GitVersion:"v1.27.2", GitCommit:"7f6f68fdabc4df88cfea2dcf9a19b2b830f1e647", GitTreeState:"clean", BuildDate:"2023-05-17T14:13:28Z", GoVersion:"go1.20.4", Compiler:"gc", Platform:"linux/arm64"}What did you do?
helm upgrade redis-operator ot-helm/redis-operator --installhelm upgrade redis-cluster ot-helm/redis-cluster --set redisCluster.clusterSize=1 --installWhat did you expect to see? A cluster with one leader and one failover node
What did you see instead? A cluster with three leader and three failover nodes