aboutsummaryrefslogtreecommitdiff
path: root/zookeeper/50pzoo.yml
Commit message (Collapse)AuthorAgeFilesLines
* 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
|
* Same startup as 51zooStaffan Olsson2017-06-281-2/+1
|
* Applies the limit to persistent zookeeper pods too. They seem more prone to ↵Staffan Olsson2017-06-281-0/+2
| | | | restarts than 51zoo.
* Upgrades to latest build from https://github.com/solsson/dockerfiles/pull/4, ↵Staffan Olsson2017-06-281-1/+1
| | | | with plain logging>=INFO config
* 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
* sStaffan Olsson2017-06-271-3/+3
|
* A monitoring-only pod uses 0m / ~32Mi resourcesStaffan Olsson2017-06-271-1/+8
|
* Adds tentative resource requests, based on what idle pods use (though this ↵Staffan Olsson2017-06-271-0/+4
| | | | includes monitoring)
* Forks can tweak storage classes, but here we want setup to be simple...zookeeper-dataStaffan Olsson2017-06-261-3/+1
| | | | | | and with the mix of PV and emptyDir there's no reason to make PVs faster than host disks. Use 10GB as it is the minimum for standard disks on GKE.
* A cluster in three availability zones now get one persistent zk each, and ↵zookeeper-availability-zonesStaffan Olsson2017-06-261-1/+1
| | | | two that can move automatically at node failures
* Makes persistence a fundamental attribute of the statefulsetStaffan Olsson2017-06-261-0/+70