aboutsummaryrefslogtreecommitdiff
path: root/zookeeper/51zoo.yml
Commit message (Collapse)AuthorAgeFilesLines
* Sets OnDelete explicitly, as RollingUpdate is a new defaultrestore-ondelete-behaviorStaffan Olsson2017-11-091-0/+2
| | | | | | | | Due to the use of config map for most of the conifg, RollingUpdate will be surprising, while still not preventing running pods that don't have the applied configuration. An automation effort would be required for proper RollingUpdate behavior.
* Updates statefulset to beta2 workload API, k8s 1.8Staffan Olsson2017-11-091-1/+5
|
* Runs Kafka 1.0.0v2.1.0Staffan Olsson2017-11-011-2/+2
|
* Shares debian with kafka-initutils -> faster first startStaffan Olsson2017-10-151-2/+2
|
* - fix #65: wait for replyElmar Weber2017-10-131-1/+1
|
* ./update-kafka-image.sh to 0.11.0.1Staffan Olsson2017-10-021-2/+2
|
* We prefer Ready:False status instead of restarted pods,Staffan Olsson2017-08-051-6/+0
| | | | | | at least for now, as it allows exec into the pods to investigate. We've been having frequent restarts that are not due to OOMKilled (i.e. not #49). Now failed probes will lead to unready pods, which we can monitor for using #60.
* Makes /metrics export opt-in (through addon branch coming up)Staffan Olsson2017-07-281-23/+0
|
* Places the myid magic number where replicas areStaffan Olsson2017-07-271-0/+3
|
* Employs the init script concept for zookeeper too, reducing duplcationStaffan Olsson2017-07-261-10/+13
|
* Default shell on Debian shows the same symptom ...Staffan Olsson2017-07-261-1/+1
| | | | | | | | of not forwarding signals as Alpine did. Kafka logs say nothing, and after 30s the container is terminated. With /bin/bash instead the log indicates shutdown behavior. This reverts commit c188f43cb8a252cd685a4944d35577ebc17a3668.
* Tagged with the policy from https://github.com/solsson/dockerfiles/pull/11Staffan Olsson2017-07-261-1/+1
|
* Clarifies a gotcha: to mount config with log4j.properties ...Staffan Olsson2017-07-261-0/+2
| | | | | | | you must use /opt/kafka/config, due to how log4j.properites (sometimes tools- or connect-) are resolved by the ./bin scripts. See https://github.com/solsson/dockerfiles/pull/10
* New build at commit 0314080Staffan Olsson2017-07-261-1/+1
|
* New build with https://github.com/solsson/dockerfiles/pull/9Staffan Olsson2017-07-251-1/+1
|
* Default shell on debian should forward signals properlyStaffan Olsson2017-07-231-1/+1
|
* solsson/kafka on debian restores installation path to /opt/kafkaStaffan Olsson2017-07-231-1/+1
|
* Upgrades to current https://github.com/solsson/dockerfiles/pull/5Staffan Olsson2017-07-231-1/+1
|
* Fixes posix compatibility for probesStaffan Olsson2017-07-231-2/+2
|
* Upgrades to latest build from https://github.com/solsson/dockerfiles/pull/4, ↵Staffan Olsson2017-06-281-1/+1
| | | | with plain logging>=INFO config
* Limiting metrics' JVM to match resource limits. Still getting OOMKilled ↵Staffan Olsson2017-06-281-2/+3
| | | | though, but maybe half as often.
* Raises memory limit for metrics; got 10 OOMKilled per pod in the last 3 hoursStaffan Olsson2017-06-271-1/+1
|
* Reduces termination grace period for zookeeper because I fail to trigger ↵Staffan Olsson2017-06-271-1/+1
| | | | termination by signal
* Adds probes, but for Kafka I don't think it indicates readiness...Staffan Olsson2017-06-271-0/+12
| | | | | | | | | | | | | | | which might not matter because we no longer have a loadbalancing service. These probes won't catch all failure modes, but if they fail we're pretty sure the container is malfunctioning. I found some sources recommending ./bin/kafka-topics.sh for probes but to me it looks risky to introduce a dependency to some other service for such things. One such source is https://github.com/kubernetes/charts/pull/144 The zookeeper probe is from https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/ An issue is that zookeeper's logs are quite verbose for every probe.
* Reverts to default termination period, and uses bash for "shell form"...Staffan Olsson2017-06-271-2/+2
| | | | | | | | as Alpine's /bin/busybox (ash) does not forward signals, according to https://pracucci.com/graceful-shutdown-of-kubernetes-pods.html The reason for the termination period change is that we haven't observed any termination behavior yet so we can't know how slow it might be.
* Got quite repeatable OOMKilled on pzoo pods, so I figured it must be...resource-limitsStaffan Olsson2017-06-271-1/+1
| | | | in metrics becuase nither zoo nor kafka has limits
* A monitoring-only pod uses 0m / ~32Mi resourcesStaffan Olsson2017-06-271-4/+11
|
* Adds tentative resource requests, based on what idle pods use (though this ↵Staffan Olsson2017-06-271-0/+4
| | | | includes monitoring)
* A cluster in three availability zones now get one persistent zk each, and ↵zookeeper-availability-zonesStaffan Olsson2017-06-261-15/+7
| | | | two that can move automatically at node failures
* Creates identical definitions for a non-persistent zoo statefulsetStaffan Olsson2017-06-261-0/+70