Live data from Hacker News

“We have been experiencing a catastrophic DDoS attack”

status.linode.com

91–100 of 151 posts

Re: “We have been experiencing a catastrophic DDoS attack”

#91
post #12

Earlier quoted context omitted.

We stuck with Linode after that, but the important parts now failover to Vultr.

We stuck with Linode after last Christmas too, but this new attack looks like the final straw. How have you found Vultr?

All's well so far! Happy to recommend them.

They seem to be the next biggest name in VPSes after Linode and DigitalOcean, with broadly similar price and quality.

Re: “We have been experiencing a catastrophic DDoS attack”

#92

I've always wondered, while in similar cases GCE/AWS can handle the traffic, is it not chargeable? So, while you will probably not get affected by the DDoS, aren't the costs going to cut your head off?

Isn't incoming data on AWS free? Or are you thinking of some kind of attack where they're using your infrastructure to amplify outgoing data?

Re: “We have been experiencing a catastrophic DDoS attack”

#93

I've always wondered, while in similar cases GCE/AWS can handle the traffic, is it not chargeable? So, while you will probably not get affected by the DDoS, aren't the costs going to cut your head off?

Isn't incoming data on AWS free? Or are you thinking of some kind of attack where they're using your infrastructure to amplify outgoing data?

Edit: I guess an attack that causes your infrastructure to auto-scale could get expensive REAL quick...

Re: “We have been experiencing a catastrophic DDoS attack”

#94
post #86

Earlier quoted context omitted.

If it's as easy and reliable as it is with Postgres (and I'd suspect it is), the answer is in my experience yes.

which tool are you using for master-master on postgres?

BDR isn't yet available in core Postgres. Postgres-BDR by a company called 2nd Quadrant seems to be the most widely used / best documented.

It can be installed as a plugin [1] and there are patched 9.4 packages available [2].

I set up a POC with databases in UK and US (east coast) last year. It was fairly straight forward and seemed to work well.

1: https://2ndquadrant.com/en/resources/bdr/ 2: http://bdr-project.org/docs/stable/index.html

Re: “We have been experiencing a catastrophic DDoS attack”

#96
post #51

Earlier quoted context omitted.

I've been wondering about this lately. Is it really feasible for a small (one man?) team to keep master-master MySQL replication over WAN running smoothly?

I'm a one man operation keeping a master-slave setup with a manual failover and it's been pretty smooth sailing once I got it setup. Don't know how much more complex master-master would be.

Same here, and as long as you understand how mysql replication works it's not too much effort to deal with. Performing the initial sync without downtime is a bit tricky, but can be done with a well-designed database and some thought. Basically you need to at least temporarily make the bulk of your data read-only, so that you can do most of the data transfer while things are running, and then only briefly lock tables on the source server for long enough to copy the stuff that has changed since the dump, and grab the binlog position. Then you copy that stuff over to the slave as well, update the slave to the correct position, and then start the slave.

That's master/slave, but to get master/master, all you need to do is start a slave on the original master and point it at the current master position on the original slave (which should be static since it isn't yet accepting any queries directly). These posts may be helpful:

https://www.digitalocean.com/community/tutorials/how-to-set-... http://plusbryan.com/mysql-replication-without-downtime

Once it's running, as long as you're not running autoincrement queries or other things that can conflict on both servers at the same time, without taking appropriate precautions, it should chug away without any intervention.

If something does go wrong, you can often figure it out by looking at the slave status, fixing the inconsistency manually, skipping the bad query, and then starting the slave. If not though, you can always just re-synchronize from scratch. Or even better, run your databases off of an LVM volume, then take regular snapshots. (IE snapshot, make a tarball of the snapshot of the mysql directory, then remove the snapshot.) That will give you a consistent backup, even with the server running. On an SSD, the temporary added latency probably won't be noticed, especially if done off-peak. Then if anything goes wrong, you can restore from the snapshot, and it should catch back up to the master from the snapshot's position automatically (as long as your expire_logs_days setting in my.cnf is longer than the duration since the snapshot was taken).

Re: “We have been experiencing a catastrophic DDoS attack”

#97

I've always wondered, while in similar cases GCE/AWS can handle the traffic, is it not chargeable? So, while you will probably not get affected by the DDoS, aren't the costs going to cut your head off?

Isn't incoming data on AWS free? Or are you thinking of some kind of attack where they're using your infrastructure to amplify outgoing data? Edit: I guess an attack that causes your infrastructure to auto-scale could get expensive REAL quick...

I'm running the maths right now.. and you could convince me to take down my side project by just having a server outside their network put wget in a loop targeted at my S3 resources.

Re: “We have been experiencing a catastrophic DDoS attack”

#99

It's not hard to compare this to brush fires. They happen periodically, and only the big trees tend to survive them. Linode is getting pretty unlucky here, but I would imagine that all the small time (and even the medium sized) hosting provides are going to succumb eventually. Is the end game just going to be Google vs. Amazon?

There are other companies which manage to deal with DDoS attacks (OVH, CloudFlare) but you're right that none of them can be described as small.

Re: “We have been experiencing a catastrophic DDoS attack”

#100
I have no evidence to support this theory, but I believe that Linode is not an outlier with regards to frequent DDOS attacks. What makes this company special seems to be with how it communicates to its customers when it's under attack.

This leads me to wonder: How much do other providers leave customers in the dark?

Post reply on HN