How actually rds parameter group is updated with multiaz failover reboot

0

Based on this document https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_RebootInstance.html

Trying to exactly understand what actually happens like the basic case below:

  1. There is a none microsoft mysql rds instance, with multiaz enabled and default parameter group
  2. Then change the default parameter group of the instance to the new custom parameter group, with pending reboot
  3. Then manually reboot the instance, in order to apply the new parameter group

According to the document, the following process would be:

  1. the secondary, standby replica becomes the new primary instance

  2. the previous primary instance becomes the new secondary, then reboot starts

  3. the new secondary(the previous primary instance) is the one that rebooted, so I can assume that the new parameter group should be applied.

  4. But the current primary instance, which has just become the primary from the secondary, didn't get a chance to be rebooted, hence doubt if the new parameter group is actually applied on it

But checking the console, the status of the parameter group is shown as in-use. How could this be?

loui
已提問 1 年前檢視次數 502 次
1 個回答
0
已接受的答案

Please note only reboot with failover results in the scenario that you have explained. And you are correct that the parameter group might not have been updated for multi-AZ instances when you invoke a reboot with failover. For reboot without failover, both the primary and secondary DB instances reboot, and parameters are updated after the reboot. Perhaps this is what you have done, and hence see the parameter group applied to primary. In any case, what I would recommend is, for applying the parameter group change for a multi-AZ RDS, always reboot without failover.

profile pictureAWS
專家
已回答 1 年前
profile picture
專家
已審閱 1 年前

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

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

回答問題指南