rigaspapas
Re:Zero downtime Postgres migration, done right
on Tuesday June 15, 2021 @07:15AM (#27513642)
Update: The cost is a good point. It wasn't that high. We actually updated the article to reflect this. It was two engineers, working full-time on it, for three weeks.
Re:Zero downtime Postgres migration, done right
on Tuesday June 15, 2021 @07:14AM (#27513635)
A few minutes of downtime wouldn't be that bad, but it would harm the company's prestige. Unlike AWS and Netflix, we are not based on massive consumption, but on a few customers. Losing one good customer can make a difference. We believe it worth the investment of time.
Re:Zero downtime Postgres migration, done right
on Tuesday June 15, 2021 @06:18AM (#27513242)
You are right. AWS DMS was our very first choice to try out. It is very easy to use, deployed within your VPC and most of the problems we mention in the article are already solved. Unfortunately, we experienced errors during our tests and the logging mechanisms were not quite helpful, so we failed to find out the problem and make it work.
Re:Zero downtime Postgres migration, done right
on Tuesday June 15, 2021 @06:14AM (#27513216)
That's a good point. We mention latency as "replication lag" and we have devoted a paragraph to the drift that comes as the result of this latency. In our case, we measured the latency to be <1s, and it was totally acceptable. As for the performance, triggers can become a problem with enough write traffic. In a different use case, Bucardo would be eliminated from a potential solution due to this.
Re:Zero downtime Postgres migration, done right
on Tuesday June 15, 2021 @06:08AM (#27513186)
We didn't mean to be arrogant with the "done right" statement. In the background story we explain how we performed the same migration once again in the past, and we end up with data loss. So this was the time that actually "did it right". Many tutorials on the Internet that describe a similar process have flows that also lead to data loss.
Re:Zero downtime Postgres migration, done right
on Tuesday June 15, 2021 @06:05AM (#27513166)
AWS can upgrade your database automatically, but with some downtime. AWS also provides DMS for migrations, which didn't work well in our case. So it was rather a simple problem at first, which turned to be a very complex one in the end.
Zero downtime Postgres migration, done right
Re:Discipline Doesn’t Scale
on Wednesday October 21, 2020 @05:09AM (#24846053)
Exactly. With so many people out there advertising themselves as "software engineers" but being "coders", companies fail to produce maintainable code without a bunch of strict rules. Coding manifestos are a must these days, otherwise you end up with a codebase that looks like the Tower of Babel.
Re:Ask HN: Who is hiring? (September 2020)
on Monday September 07, 2020 @04:43AM (#24397747)
Blueground | Senior DevOps Engineer | Athens (GR) or REMOTE | https://apply.workable.com/blueground/j/96E4BD6F9C/
We seek for someone who can help us to Kubernetize our infrastructure. Prior experience is a big plus, but not strongly required. We are based in Athens, but remote work is also possible from a similar timezone.
Ask HN: Where to Search for Remote Jobs?
Do you have any platform to suggest in order to search for remote jobs?
Common Hiring Mistakes
Fighting climate change with trees is like emptying a sinking boat with a spoon
Re:Update in ajv package broke webpack
on Saturday February 09, 2019 @08:00PM (#19125756)
This is what happens when you don't pin your dependencies, right?
Why I wrote a utility for diagnosing paths
Do you improve your online privacy by removing the `Referer` header?
Re:Show HN: %%30%30: A Game
on Sunday September 20, 2015 @07:09PM (#10249571)
This game has free graphics upgrade if you use "Emoji Input by EmojiStuff.com" extension
Re:Monitor your local network with Raspberry Pi
on Tuesday September 15, 2015 @11:38AM (#10221239)
Would arpwatch provide any extra information? Ntop sounds like a very interesting idea, I wasn't aware. I suppose you mean you can use a wireless card on you Pi, so the clients can connect through it, and then use ntop to measure the usage... Right?
Re:Monitor your local network with Raspberry Pi
on Tuesday September 15, 2015 @11:35AM (#10221219)
Just some rewrite rules to prettify the URL. It's a ghost blog, running in port 2368.
Re:Monitor your local network with Raspberry Pi
on Tuesday September 15, 2015 @11:30AM (#10221191)
Can you give me a hint about that? Wouldn't that be too much for a Pi?
Re:Monitor your local network with Raspberry Pi
on Tuesday September 15, 2015 @11:27AM (#10221171)
Just to save time and practice skills. It's faster, since it doesn't require passwords, and more responsive and beautiful, since it uses bootstrap.
Re:Monitor your local network with Raspberry Pi
on Tuesday September 15, 2015 @11:22AM (#10221144)
There are some routers providing these information through their web interface, but I haven't found anyone that provides these info through SSH. Any ideas how I could grab that information?
Re:Monitor your local network with Raspberry Pi
on Tuesday September 15, 2015 @11:15AM (#10221112)
I believe you about openWRT awesomeness, but unfortunately, my router isn't fully compatible, so I tried to come up with an alternative.
Re:Monitor your local network with Raspberry Pi
on Tuesday September 15, 2015 @11:07AM (#10221064)
If you want to see what clients are connected to your network you have to login into your router (typing username & password), navigate to its WiFi or DHCP client tables and then try to match MAC addresses with real clients. What I tried to do is mostly time saving. You can have information about hostnames, MACs, MAC manufacturers and status via the web.