Anisha K J created ZOOKEEPER-4530:
-------------------------------------
Summary: Dynamic config file is not updated while scaling down
zookeeper replicas
Key: ZOOKEEPER-4530
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-4530
Project: ZooKeeper
Issue Type: Bug
Components: server
Affects Versions: 3.8.0
Reporter: Anisha K J
Fix For: 3.8.0
# create zk cluster with 3 replicas
# kubectl edit zookeeopercluster , change replica to 1
# we can see that pod count is 1
# Loginto {{kubectl exec -it zookeeper-0 /bin/bash}} and see the contents of
{{cat /data/conf/zoo.cfg}}
{code:java}
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 {code}
5. cat /data/conf/zoo.cfg.dynamic.200000013
#
{code:java}
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
{code}
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
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
