etcd

13 engineers on Hacker News describe using etcd first-hand: 5 endorse it, 4 regret it, 0 are mixed.

52%trust
13first-hand users
11in production
endorse 5mixed 0regret 4uses, no opinion

“As my K8s clusters crashed irrecoverably in many different ways (etcd, pvcs, velero, hdd failures, shared storage, databases)”

regret · personal · figassis · 2023-08-28 · source ↗ · wrong label?

“For us it was cluster certificate expiration and etcd corruption, and some other problems we couldn't ever pin down.”

regret · production · throwaway20371 · 2021-11-01 · source ↗ · wrong label?

“etcd/kafka/redis (if you can consider those a database) inside docker/crio inside k8s. In production under high load.”

endorse · production · dilyevsky · 2021-07-28 · source ↗ · wrong label?

“etcd/zk/consul is battle tested and did work even that we have way more network partitions than your typical network”

endorse · production · merb · 2017-12-06 · source ↗ · wrong label?

“I have had these issues with Etcd, using the default CoreOS configuration of Etcd, and I've not had these issues with Gluster”

regret · production · vidarh · 2016-06-01 · source ↗ · wrong label?

“running test clusters with just fleet, using custom bash and etcd for service discovery. Works fine”

endorse · personal · ownagefool · 2015-11-22 · source ↗ · wrong label?

“etcd ships with CoreOS, and when I spin up a new cluster via Cloudformation it's up and waiting for me as soon as I log in. This is a huge selling point”

endorse · production · namecast · 2015-09-11 · source ↗ · wrong label?

“We had some trouble with etcd at work with constant leader re-election and high CPU usage around last summer”

regret · production · vruiz · 2015-02-10 · source ↗ · wrong label?

“we've worked with enough production Deis deployments to know that etcd and fleet (for example) run much better than some might think.”

endorse · production · gabrtv · 2014-11-11 · source ↗ · wrong label?

“Just to name the ones we use at Helsinki City.”

neutral · production · gatestone · 2021-12-25 · source ↗ · wrong label?

“discovery.etcd.io, a service we run to make it easier to bootstrap new etcd quorums, is just a quorum of etcd nodes”

neutral · production · jzelinskie · 2017-05-20 · source ↗ · wrong label?

“Please +1 the thing on GitHub and we will try and get it fixed in prod”

neutral · production · philips · 2016-06-30 · source ↗ · wrong label?

“We had to write our own orchestrator on top of Etcd to get the functionality we wanted.”

neutral · production · tinco · 2015-11-22 · source ↗ · wrong label?