[ZOOKEEPER-4530] Dynamic config file is not updated while scaling down zookeeper replicas

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 3.8.0
• Fix Version/s: 3.8.0
• Component/s: server
• Assignee: Unassigned
• Reporter: Anisha K J
• Created: 25/Apr/22 14:32
• Updated: 02/Nov/23 09:26

Description

1. create zk cluster with 3 replicas
2. kubectl edit zookeeopercluster , change replica to 1
3. we can see that pod count is 1
4. Loginto kubectl exec -it zookeeper-0 /bin/bash and see the contents of cat /data/conf/zoo.cfg

   cat /data/conf/zoo.cfg
   metricsProvider.exportJvmInfo=true
   dataDir=/data
   4lw.commands.whitelist=cons, envi, conf, crst, srvr, stat, mntr, ruok
   syncLimit=2
   commitLogCount=500
   metricsProvider.httpPort=7000
   snapSizeLimitInKb=4194304
   standaloneEnabled=false
   metricsProvider.className=org.apache.zookeeper.metrics.prometheus.PrometheusMetricsProvider
   initLimit=10
   minSessionTimeout=4000
   snapCount=10000
   admin.serverPort=8080
   autopurge.purgeInterval=1
   maxSessionTimeout=40000
   maxCnxns=0
   globalOutstandingLimit=1000
   reconfigEnabled=true
   skipACL=yes
   autopurge.snapRetainCount=3
   tickTime=2000
   quorumListenOnAllIPs=false
   preAllocSize=16384
   maxClientCnxns=60
   dynamicConfigFile=/data/conf/zoo.cfg.dynamic.200000013 

   5.  cat /data/conf/zoo.cfg.dynamic.200000013  

1. apache-zookeeper-3.8.0-bin# cat /data/conf/zoo.cfg.dynamic.200000013
   server.1=zookeeper-0.zookeeper-headless.default.svc.cluster.local:2888:3888:participant;0.0.0.0:2181
   server.2=zookeeper-1.zookeeper-headless.default.svc.cluster.local:2888:3888:participant;0.0.0.0:2181
   server.3=zookeeper-2.zookeeper-headless.default.svc.cluster.local:2888:3888:participant;0.0.0.0:2181r 

Issue: No new dynamic config file is created, and config file shows  3 entries even if there is only one. Same issue is not seen with zookeeper 3.7.0 and 3.6.3