Ahh. Good to know. I do prefer that method, personally.
Will updates about Postgres always go into that thread? I hadn’t read the entire discussion and wasn’t subscribed to that one. If that’s how changes will be communicated, I’ll subscribe to the thread. Otherwise, a new forum topic would be helpful to highlight changes to the service that may require us to do things differently.
Yeah we’ll keep updating that thread! It’s a good one to subscribe to.
Not sure if related at all, I‘m experiencing an outage today.
Here’s a log snippet from the primary (?)
[info] keeper | 2022-10-24T19:28:23.791Z ERROR cmd/keeper.go:870 failed to update keeper info {"error": "Unexpected response code: 500 (rpc error making call: leadership lost while committing log)"}
[info] sentinel | 2022-10-24T19:28:23.891Z ERROR cmd/sentinel.go:1843 error retrieving cluster data {"error": "Unexpected response code: 500"}
I’ve also noticed an immensely large replication lag in the metrics. All other metrics in Grafana (memory, cpu load, volume) seem okay though.