It is possible just to update just the YAML for Zookeeper. However, as many people have forked the helm chart, updating to the latest helm chart may be time-consuming. Image : docker.io/library/zookeeper:3.8.0 For those who cannot easily upgrade the helm chart Kubectl get pod -n default zk-0 -o yaml | grep image Then run the following, changing my-release to match the release name of your releaseĪfter the upgrade has taken you should see the newer version of zookeeper on your pods # The Zook eeper image used in the cluster. Then update the values.yaml file under the zookeeper tag to look like the following: # Zook eeper To fix this, the easiest approach is to upgrade the helm chart from the source by running the following command where you checked the source out: git pull origin master usr/bin/start-zookeeperĮcho "autopurge.purgeInteval=$PURGE_INTERVAL" > $CONFIG_FILEĪs you can see, Interval is misspelled as Inteval, and therefore, the configuration file is never correctly set. Which you can see here or by running the following command with docker installed dremio_v2 (master) ✗ docker run -it /kubernetes-zookeeper:1.0-3.4.10 grep purge\.purge. The docker version of zookeeper we were using had a typo for the purge interval, disabling purge permanently.
kubectl get pod -n default zk-0 -o yaml | grep image Details Applies ToĪll versions of the helm chart that are still using the older /kubernetes-zookeeper zookeeper image, which you can find out by running the following on your deployment (change -n to match the namespace where you have deployed dremio). The disk will fill up on zookeeper pods as the logs and snapshots never purge.
0 kommentar(er)
