s5cmd is not listed here https://www.rsync.net/resources/howto/remote_commands.html ? :-)

It either was added in the meantime or it already was there

> Backup Tools

> attic, borg (usage notes), rclone, unison, s5cmd and git are installed (on our server side).

> You would most likely call these commands by running these tools locally and connecting to rsync.net with them.

Great read!

But...

“Can you check /var/log/messages and see if there’s messages every 30 minutes about ENA going down and then back up?”

Isn't this "sysadmin 101" ? Like... the first thing to check on any server exhibiting weird behaviour ? :-) A message about a NIC going up & down every 30min would have triggered many here instantly.

Interesting journey nevertheless!

It’s probable that they did do that, but also that the network issue didn’t appear related, even though it’s suspect on its own.

Thank you! Had to scroll way too much to read that.

On production systems "reclaimPolicy: Retain" on the storageClass feels like a no brainer to (mostly) avoid such disaster.

Nice writing, investigation and findings that will benefit to a lot!

The before/after graphs are impressive.

Thanks Cloudflare falks

No, OpenAI's plugin system uses OpenAPI: https://platform.openai.com/docs/plugins/introduction

Ah, I think you're right!

You should have a look at https://github.com/citusdata/pg_auto_failover

This project makes is super easy to setup a resilient and highly-available postgresql cluster.

And since the postgresql client lib handle connection to multiple replica... no need for some kind of load-balancer (pg_bouncer, pgpool...) in front of it anymore (even if they can still be useful sometimes).

pgbouncer is not a load balancer, it's a connection pooler.

The former is used to split reads and writes (and so far I haven't seen "magic" tools that automate it well, pgpool has lots of issues; this task is better to solve in app code -- most modern frameworks either already solved it such as RoR, or at least work well with 2 connections),

the latter is used to multiplex connections and improve performance similarly to nginx, haproxy, envoy, but with native Postgres protocol support.