Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Fixes posix compatibility for probes | Staffan Olsson | 2017-07-23 | 1 | -2/+2 |
| | |||||
* | Upgrades to latest build from https://github.com/solsson/dockerfiles/pull/4, ↵ | Staffan Olsson | 2017-06-28 | 1 | -1/+1 |
| | | | | with plain logging>=INFO config | ||||
* | Limiting metrics' JVM to match resource limits. Still getting OOMKilled ↵ | Staffan Olsson | 2017-06-28 | 1 | -2/+3 |
| | | | | though, but maybe half as often. | ||||
* | Raises memory limit for metrics; got 10 OOMKilled per pod in the last 3 hours | Staffan Olsson | 2017-06-27 | 1 | -1/+1 |
| | |||||
* | Reduces termination grace period for zookeeper because I fail to trigger ↵ | Staffan Olsson | 2017-06-27 | 1 | -1/+1 |
| | | | | termination by signal | ||||
* | Adds probes, but for Kafka I don't think it indicates readiness... | Staffan Olsson | 2017-06-27 | 1 | -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 Olsson | 2017-06-27 | 1 | -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-limits | Staffan Olsson | 2017-06-27 | 1 | -1/+1 |
| | | | | in metrics becuase nither zoo nor kafka has limits | ||||
* | A monitoring-only pod uses 0m / ~32Mi resources | Staffan Olsson | 2017-06-27 | 1 | -4/+11 |
| | |||||
* | Adds tentative resource requests, based on what idle pods use (though this ↵ | Staffan Olsson | 2017-06-27 | 1 | -0/+4 |
| | | | | includes monitoring) | ||||
* | A cluster in three availability zones now get one persistent zk each, and ↵zookeeper-availability-zones | Staffan Olsson | 2017-06-26 | 1 | -15/+7 |
| | | | | two that can move automatically at node failures | ||||
* | Creates identical definitions for a non-persistent zoo statefulset | Staffan Olsson | 2017-06-26 | 1 | -0/+70 |