Re:Torus: A distributed storage system by CoreOS
by dang on Thursday June 02, 2016 @04:38PM
(#11825837)
> I love that I know who this is at CoreOS by the choice of username
You can't comment like this here. It's a breach of civility and took the conversation in a needlessly personal direction. Please don't do this again.
We detached this subthread from https://news.ycombinator.com/item?id=11818589 and marked it off-topic.
Re:Torus: A distributed storage system by CoreOS
by alexandre_m on Wednesday June 01, 2016 @11:53PM
(#11820246)
Cockroachdb is built on top of etcd. So far seems to work very well for their product.
I think this whole thread is a bit harsh and unfair to CoreOs and their solutions.
Re:Torus: A distributed storage system by CoreOS
by vidarh on Thursday June 02, 2016 @12:35AM
(#11820395)
I think that reflects the complexity of a storage product more than CoreOS itself. I use CoreOS. I like it. I love the update mechanism, and the tight focus on running as much as possible in containers.
But I also have spent enough time using it to run across certain warts, and Etcd clusters refusing to start without manual intervention etc. have been a frequent enough problem that when they go after something incredibly hard such as distributed storage, and it's relying on Etcd, I see that as a scary combination.
Re:Torus: A distributed storage system by CoreOS
by gyuho on Thursday June 02, 2016 @12:19AM
(#11820339)
Disclaimer: I work on etcd at CoreOS.
CockroachDB is built on top of etcd/raft package, not etcd itself.
Re:Torus: A distributed storage system by CoreOS
by jedisfullofit on Thursday June 02, 2016 @02:26PM
(#11824879)
While we're talking about who is who -- the parent poster is Jed Smith; he's a sysadmin and disgruntled former CoreOS employee. I'd take what he says with more than a grain of salt.
On topic, yes. It is quite trivial to lose data with etcd and pretty much everybody I know who runs it has experienced problems. Try backing it up and restoring. etcd is compsci great yet operationally burdensome; it is extremely difficult to operate, tends to make assumptions and explain to you how to operate your fleet, and the developers are not very receptive to these and other operational concerns. This stems from CoreOS culture, to be quite clear -- CoreOS seeks to eliminate operations as a discipline and replace it with software, and tends to disregard or devalue operational concerns as a result.
Launching down the storage path with Go software and disregarding several decades of operational experience in the industry on how to do distributed storage correctly (not to mention the "looking down" on etcd-related infrastructure decisions from this anonymous employee) should indicate to you that I'm not making this up, despite how it may appear.
90% of folks I know on etcd, I'd estimate, have (a) reverted to Zookeeper or (b) moved on to Consul. It is the single piece of software that is holding Kubernetes back, too, and it's fairly obvious from roadmap direction that Kubernetes is now the etcd customer. Plan accordingly.