Live data from Hacker News

Yelp rebuilds corrupted Cassandra cluster using its data streaming architecture

infoq.com

51–53 of 53 posts

Re: Yelp rebuilds corrupted Cassandra cluster using its data streaming architecture

#51

Earlier quoted context omitted.

Hosted k8s to run a few docker image is almost no extra work and possibly less work than setting up your own docker hosting system. I see a small hosted k8s setup with a hosted sql server as a fine app for many things.

True, but it's a complete waste if all you need is a single webapp and you're running it on something like Azure anyway which can just run that single Docker image. In this case you had a potential zero management environment, truly Cloud as it was meant to be, vs. managing Kubernetes, plus a database. You could go with managed Kubernetes (AKS) and a managed SQLServer, but why take on that cost? Edit: Even AKS isn't…

So that is why I said to use GCE not Azure, of course Azure is extra work ;P use GKE.

I have personally never build an app that was a single docker image running. Usually I am at a min of 2. One server going down shouldn't take down prod once you even have 1 paying customer.

Re: Yelp rebuilds corrupted Cassandra cluster using its data streaming architecture

#53
post #6

What is a bit unclear which isn't addressed in the original blog post is how they actually were able to successfully scan over all the data and copy it to the new cluster, in spite of corrupt sstables. CDC would not handle back filling historical data. Would expect that to fail for certain token ranges. Perhaps they ended up deciding to discard them?

[deleted]
Post reply on HN