max_wal_senders invalid setting

0

Hi guys,

We have a single Postgresql 10 rds instance replicating to another instance and haven't changed any default parameters
We had a brief outage on Sunday, looking at the event logs on the main server we see the following:

Sun, 10 Mar 2019 13:11:11 GMT Recovery of the DB instance has started. Recovery time will vary with the amount of data to be recovered.
Sun, 10 Mar 2019 13:15:27 GMT The parameter max_wal_senders was set to a value incompatible with replication. It has been adjusted from 10 to 15.
Sun, 10 Mar 2019 13:16:01 GMT Recovery of the DB instance is complete.
Sun, 10 Mar 2019 13:16:28 GMT The parameter max_wal_senders was set to a value incompatible with replication. It has been adjusted from 10 to 15.
Sun, 10 Mar 2019 13:16:31 GMT DB instance restarted

I'm not entirely sure from this what the cause of the outage was... looking at the default parameters our max_wal_senders is set to 10 still

Does anyone have any ideas how a) i can work out what happened? and b) if 10 is actually a valid value for that setting?

thanks!

Dan

danturn
已提問 5 年前檢視次數 4636 次
2 個答案
0

Message: "The parameter max_wal_senders was set to a value incompatible with replication. It has been adjusted from 10 to 15.","

Please be assured the above message is a known message when an RDS instance is restarted, this event is harmless and has no performance impact on the instance. Kindly note that the internal team is aware of this event occurrence and is working on rolling out a fix.
Hence, currently, there is no requirement of setting up the above parameter and you can safely ignore this Warning message until the internal team rolls out a fix at the backend.

Unfortunately, I do not have a valid ETA for when the fix will be rolled out by internal team, however please be assured that this message is harmless and it's level is "Warning" and no action is required from your end.

已回答 5 年前
0

ok, thanks for that

danturn
已回答 5 年前

您尚未登入。 登入 去張貼答案。

一個好的回答可以清楚地回答問題並提供建設性的意見回饋,同時有助於提問者的專業成長。

回答問題指南